gecko-dev/layout/reftests/usercss
Emilio Cobos Álvarez 0e897301b5 Bug 1394233: Quirks mode changes can happen after a flush. r=xidorn
The reason why bug 1355721 regressed this is because in non-e10s we definitely
flush before parsing the standards quirks-mode. And bug 1355721 introduced an
unconditional UpdateStylistIfNeeded, unless the counter style / font
equivalents.

That means that the stylist wouldn't remain on its initial state after the first
flush, which itself means that when the compat mode changed, the UA and user
rules were already on the stylist with the quirks mode keys. That makes
class-names be keyed in ascii lowercase.

After that no user style changed, so no rebuild happens for the cascade data in
the user origin, so we keep looking at the wrong keys indefinitely.

MozReview-Commit-ID: 25dD2bca3tN
2018-02-11 20:06:28 +01:00
..
reftest.list Bug 1394233: Quirks mode changes can happen after a flush. r=xidorn 2018-02-11 20:06:28 +01:00
usercss-moz-document-ref.html Bug 1358524 - Load userContent.css on both style backends in e10s. r=bholley 2017-05-03 20:48:48 +09:00
usercss-moz-document.html Bug 1358524 - Load userContent.css on both style backends in e10s. r=bholley 2017-05-03 20:48:48 +09:00
usercss-ref.html Bug 1358524 - Load userContent.css on both style backends in e10s. r=bholley 2017-05-03 20:48:48 +09:00
usercss-uppercase.html Bug 1394233 - Reftest to ensure that uppercase class names work. r=test-only 2017-09-16 16:12:28 +09:00
usercss-xbl.html Bug 1358524 - Load userContent.css on both style backends in e10s. r=bholley 2017-05-03 20:48:48 +09:00
usercss.html Bug 1358524 - Load userContent.css on both style backends in e10s. r=bholley 2017-05-03 20:48:48 +09:00