-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beware of overflow: hidden, it breaks z-translation quite badly #493
Comments
Is this happening in all browsers, or only a specific vendor? |
Z-ordering issues inside the ContainerSurface seem to happen on Chrome. Z-ordering conflicts outside the ContainerSurface on safari and Firefox, haven't tested with IE though |
Can you provide test cases? This is something we see break often as browsers roll out new versions. |
I created a test project for it: |
Fantastic tests. Thanks for sending these. |
Can you send me your browser versions? THanks! |
Chrome Version 38.0.2125.122 |
I am not sure if I misread your comment 2 hours ago but I am seeing no issues on Safari and Firefox. This seems to be only a Chrome issue for me. My version of your tests Screenshots: |
Wrong Safari Screenshot. Edited above. |
That is just the bottom right overlapping the top right which is not an issue. The four quadrants are technically at the same z depth as far as the browsers are concerned which means it is just left to DOM order. If you rearrange your code to have the each quadrant render in a different order you will see different results. |
Mike, When using overflow: hidden, the divs inside the ContainerSurface seem to overlap the divs outside on all major browsers, not respecting the z-translation. This behaviour occurs on Safari and Firefox, so it almost seems by design. Quite strange really. |
When outside of the ContainerSurface, essentially think of them as flattening out and existing as a single Surface. The depths of things inside the ContainerSurface does not matter across ContainerSurfaces. |
Right, I see. So in that case the z-index of the ContainerSurface itself would be used, is that correct? |
Exactly. |
@michaelobriena Can you post your version with the quadrants separated? |
I made a bug for it in the Chromium bug tracker, https://code.google.com/p/chromium/issues/detail?id=456601&thanks=456601&ts=1423425515 |
Sorry, I actually just cleaned that up Friday! |
No prob. hehe |
Looks like they've confirmed it is a bug on their side: https://code.google.com/p/chromium/issues/detail?id=456601#c2 |
Update: The chromium devs have found the version that caused the break, and are looking to fix it. |
@jordangarside What's the expected behavior? What should I see vs what we're actually seeing? |
I believe Chrome fixed this at one point a few months ago and then regressed. The bug appears to occur specifically when both For example, @jordangarside in the example you linked, if you use to chrome inspector to remove the |
This has been fixed in Chrome |
Awesome! Which version was that? |
@IjzerenHein Unfortunately all I have for you is sometime between today and Nov 24th 2014 |
Alright, well thanks for sharing that Michael! |
Hi, I've come across a very annoying browser issue that causes the z-translation to not be respected. It happens to renderables inside a ContainerSurface using 'overflow: hidden'. Basically, the z-translation is no longer respected and instead the DOM ordering is used.
Obviously this is not a famo.us bug, but I thought you should know.
Test project: https://github.com/IjzerenHein/famous-zindex
Regards, Hein
The text was updated successfully, but these errors were encountered: