mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-11-11 13:48:23 +02:00
5ee9269405
In particular, even when there are no frames, we may have used the rule cascades / stylist data (for different stuff, like font-feature-values, thus the regressing bug). Using the old rule cascades / stylist data without knowing it has changed is wrong, thus the bug. Now that media query change stuff is async and has a well-defined processing point, we should be able to just call it without too much worry. Also note that at the point the extra hints are passed, if there's no root frame / elements are not styled / etc, we'll optimize away the change hint. The test-case intermittently fails without this patch, but I didn't manage to make a better one, unfortunately :( MozReview-Commit-ID: LY2HRIlAKHX
9 lines
227 B
HTML
9 lines
227 B
HTML
<!doctype html>
|
|
<meta charset="utf-8">
|
|
<title>CSS Test Reference</title>
|
|
<link rel="author" href="mailto:emilio@crisal.io">
|
|
<meta name="viewport" content="width=300">
|
|
<style>
|
|
p { color: green; }
|
|
</style>
|
|
<p>Should be green</p>
|