Bug 1603918 Comment 10 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
florian/dao, what I believe is happening now is without the MozAfterPaint -> FirstNonBlankPaint listeners and async messages (which were triggered by about:home painting something), the `browser[blank] { opacity: 0 }` [0] is no longer hiding the initial white page of about:home, which gets its styles set with an async LightweightTheme:Set message [1]. There has been a race condition even without the workaround removal, and as suggested in comment 4, this is easily reproduced by reloading the page without a new window, so there's an underlying issue of the page first painting light then dark.

[0] https://searchfox.org/mozilla-central/rev/c61720a7d0c094d772059f9d6a7844eb7619f107/browser/base/content/tabbrowser.css#81 is
[1] https://searchfox.org/mozilla-central/source/browser/base/content/contentTheme.js
Revision 1 by
on 
florian/dao, what I believe is happening now is without the MozAfterPaint -> FirstNonBlankPaint listeners and async messages (which were triggered by about:home painting something), the `browser[blank] { opacity: 0 }` [0] is no longer showing the background set on `tabbrowser-tabpanels`, i.e., hiding the initial white page of about:home, which gets its styles set with an async LightweightTheme:Set message [1]. There has been a race condition even without the workaround removal, and as suggested in comment 4, this is easily reproduced by reloading the page without a new window, so there's an underlying issue of the page first painting light then dark.

[0] https://searchfox.org/mozilla-central/rev/c61720a7d0c094d772059f9d6a7844eb7619f107/browser/base/content/tabbrowser.css#81 is
[1] https://searchfox.org/mozilla-central/source/browser/base/content/contentTheme.js
Revision 2 by
on 
florian/dao, what I believe is happening now is without the MozAfterPaint -> FirstNonBlankPaint listeners and async messages (which were triggered by about:home painting something), the `browser[blank] { opacity: 0 }` [0] is no longer showing the background set on `tabbrowser-tabpanels`, i.e., hiding the initial white page of about:home, which gets its styles set with an async LightweightTheme:Set message [1]. There has been a race condition even without the workaround removal, and as suggested in comment 4, this is easily reproduced by reloading the page without a new window, so there's an underlying issue of the page first painting light then dark.

[0] https://searchfox.org/mozilla-central/rev/c61720a7d0c094d772059f9d6a7844eb7619f107/browser/base/content/tabbrowser.css#81
[1] https://searchfox.org/mozilla-central/source/browser/base/content/contentTheme.js

Back to Bug 1603918 Comment 10