On Thu, Nov 4, 2010 at 6:35 PM, Sylvain Galineau <sylvaing@microsoft.com>wrote:
> It **is** different from the content without a transform, that’s why it’s
> confusing. The pre-transform content causes no overflow whatsoever. Since
> scaling of that content is what causes the overflow I can’t expect the
> scrollbar to affect what the transform scales.
>
>
>
> I understand the rendering for overflow:scroll. For overflow:auto, it’s as
> if you figure out whether the transformed element will cause overflow then
> reflow it as if scrollbars where there before transforming it. I don’t think
> that makes sense.
>
I continue to claim that exactly the same thing can happen with
non-transformed content. You "figure out whether the content will cause
overflow, then reflow it as if scrollbars were there."
Of course, what we all actually do in that situation is iterate. In Gecko
our scrollbar layout code needed no additional work to handle the presence
of transforms.
Modulo the scrollbars needed to see the content, I think expect the
> overflow:auto case to look just like the overflow:visible one.
>
I think that would be weird. You'd be saying that with overflow:auto, the
presence of a scrollbar affects the layout of descendant elements, except
for those that are transformed.
Rob
--
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]