Closed Bug 1269184 Opened 4 years ago Closed 4 years ago
CSS perspective and z-index not layered properly on Firefox 46+, breaking site navigation on ESPN FC and ADS-B Exchange
A Firefox 46 site-compat regression posted on Firefox Input: https://input.mozilla.org/en-US/dashboard/response/5899062 STR: 1. Go to http://www.adsbexchange.com/ 2. Click on Global Radar View to open the map 3. Click on the Menu at the top left corner of the map Actual: The menu will not open. <div class="dl-menuwrapper"> is rendered behind the map. Expected: The menu will open. <div class="dl-menuwrapper"> should be visible on top of the map. Good: Firefox 45, 48 DevEdition, 49 Nightly Bad: Firefox 46, 47 Beta
[Tracking Requested - why for this release]: Break a website Regression window (w/ disable e10s & disable APZ): https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4c9e1d2a80264ba8767b01c31eb75010b03bb076&tochange=90f7eaeca546a96d2c897c5bcc68f84e6885d7c9 Regressed by 2f38c18c7c16 Matt Woodrow — Bug 1230774 - Use correct Z order to sort perspective items. r=roc And I can also reproduce the problem on Aurora48.0a2 and Nightly49.0a1 if disable e10s & disable APZ.
Thank you Alice-san!
Has Regression Range: --- → yes
Has STR: --- → yes
Assignee: nobody → matt.woodrow
Attachment #8748056 - Flags: review?(mstange)
Attachment #8748056 - Flags: review?(mstange) → review+
Probably too late for 46 so won't fix. But we will track for other branches.
46.0.1 is being planned, right? ADS-B Exchange is a small site, but ESPN FC, reported in Bug 1268590 as well as Firefox Input, is probably a high profile site. If the risk is low (seems so) we should fix it without waiting for 47.
Posted the site compatibility doc: https://www.fxsitecompat.com/en-CA/docs/2016/combination-of-css-perspective-and-z-index-leads-to-wrong-layering/
[Tracking Requested - why for this release]: Re-nominating for 46.0.1, see my Comment 6.
46.0.1 came out today. I didn't see this till after we built and released. We can keep this open and track it in case we end up doing another point release. For now let's fix this on m-c and uplift as far as it can go!
Hello Matt, should we consider uplifting this to Beta47 and Aurora48? If yes, please nominate for uplift. Thanks!
I think this is also fallout from this bug: https://github.com/webcompat/web-bugs/issues/2529#issue-153492426 mozregression led me here: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=aef562eaad80d8c5bc4b1ba97c653e71593c6b79&tochange=23bf1e82cc3425e7e1d1224dd1723916a084507e I would suggest uplifting as far as it can go (if it's safe).
Comment on attachment 8748056 [details] [diff] [review] Create an nsDisplayWrapList for perspective frames so we take their z-index into account Approval Request Comment [Feature/regressing bug #]: Bug 1230774 [User impact if declined]: z-index combined with perspective broken [Describe test coverage new/current, TreeHerder]: Manually tested, reftest added [Risks and why]: Pretty low risk, just changing paint order sorting. [String/UUID change made/needed]: None
Comment on attachment 8748056 [details] [diff] [review] Create an nsDisplayWrapList for perspective frames so we take their z-index into account Recent regression, Aurora48+, Beta47+
Sorry, have to ask: is a fix coming also for version 46.0.x? This is a pretty big breakage and several other websites are affected as well.
Do you have a list of the affected sites? Looks like http://www.espnfc.us/ has already implemented a workaround for the issue themselves.
(In reply to Kohei Yoshino [:kohei] from comment #19) > Do you have a list of the affected sites? Sorry, not right away but I will list the problematic sites here as I come across them, > Looks like http://www.espnfc.us/ > has already implemented a workaround for the issue themselves. I don't see where. The site is still completely unusable to me.
http://www.iplt20.com/match/2016/50 Click on any of the videos in the section "Match Recap". The flash video starts playing but you cannot actually see the video (just a black area instead) as it seems to be playing "under" the area.
The fix is coming in 47, if it hasn't already been addressed by individual sites. Wontfix for 46.
You need to log in before you can comment on or make changes to this bug.