Re: Issue 113450 in chromium: -webkit-transform: translateZ changes behavior in Chrome 17+

[chro...@googlecode.com]

Comment #5 on issue 113450 by daniel...@google.com: -webkit-transform:
translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

Here's a basic replica of the original problem:
https://oreo-android.googlegoro.com/zindex-chrome-bug.html

4 elements translated negatively across the z-axis at -400px per element.
So they're located at the following depths, respectively:

0 => 0px
1 => -400px
2 => -800px
3 => -1200px

There is a content container wrapping these child elements that translates
in the positive z direction at 0, 400, 800, and 1200.

Perspective value is set to 600.

When the content container is translated to a z-position greater than OR
equal to the perspective value (i.e. 600px), mouse focus is lost inside the
container and all child elements within.

Let me know if you have any questions.

[chro...@googlecode.com]

Comment #12 on issue 113450 by daniel...@google.com: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

I don't have an account at https://bugs.webkit.org/. I could create one,
but I was hoping someone on Chromium could quickly do a cross-post of the
issue.

Shawn or someone else, can you please cross-post this issue there?

[chro...@googlecode.com]

Comment #24 on issue 113450 by wiltz...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

FYI, it looks like:

https://oreo-android.googlegoro.com/zindex-chrome-bug.html

now works, but

http://savedbythegoog.appspot.com/?id=b786acdbedaced58c9f5361a4b5fefae00807b7c

still has issues with both clipping when the active div is switched and
selecting the input box.

I can't repro the original android site anymore because I think it's
changed?

[chro...@googlecode.com]

Comment #25 on issue 113450 by wiltz...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

Quick ping for an update again; I know there's lots of work going on in
this general area but checking in. Thanks,

[chro...@googlecode.com]

Comment #26 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

So far so good:
http://trac.webkit.org/changeset/113364
http://trac.webkit.org/changeset/113606

Those CLs fix the perspective issues for rendering bugs. There are 1-2
more CLs that are needed to fix the rendering bugs completely. After that
I will visit the hit-testing bugs, which may require merging that code to
WebCore.

[chro...@googlecode.com]

Comment #29 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

I submitted a fix for review at
https://bugs.webkit.org/show_bug.cgi?id=79136

With any luck it will get approved soon, and hopefully it will make it into
m20 before branch =)

[chro...@googlecode.com]

Comment #30 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

Just landed http://trac.webkit.org/changeset/116543

I'll close this bug after it rolls into canary and I can double-check that
its actually fixed.

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #31 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

Hi all, this is fixed on latest canary.

Please note there is a separate regression on that page where layers
flicker when clicking to interact with them. I'm pretty sure this is
unrelated, and created
https://code.google.com/p/chromium/issues/detail?id=127683 to continue
looking at that issue.

[chro...@googlecode.com]

Comment #34 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

This hit-testing demo has broken again just today. It works on canary, but
stopped working on tip of tree, so it probably broke between webkit r117808
and r118118.

I tried reverting a few "suspicious" recent CLs that may have been
releated, but none of them seemed to be the cause of the regression.

I'm trying to use git bisect right now, and hopefully I can identify how it
broke and ask them to fix it...

[chro...@googlecode.com]

Comment #35 on issue 113450 by shawnsi...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

I bisected this down to http://trac.webkit.org/changeset/117815, and
reported the bug at
https://code.google.com/p/chromium/issues/detail?id=129314

I think this bug can remain closed, and the regression fix should happen on
that new bug report.

[chro...@googlecode.com]

Comment #36 on issue 113450 by dan...@chromium.org: -webkit-transform:

translateZ changes behavior in Chrome 17+
http://code.google.com/p/chromium/issues/detail?id=113450

Oh, I also bisected this, and achieved the same result. Hooray for
consistency.