Closed
Bug 1345218
Opened 8 years ago
Closed 7 years ago
stylo: shorthand serialization doesn't match Gecko
Categories
(Core :: CSS Parsing and Computation, enhancement, P2)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: jdm)
References
Details
Some testcases:
<body style="border-top: 1px solid green; border-color: red;">
<script>document.writeln(document.body.style.cssText);</script>
<body style="border-color: red; border-top: 1px solid green">
<script>document.writeln(document.body.style.cssText);</script>
Plus of course we need to pass layout/style/test/test_shorthand_property_getters.html
Reporter | ||
Comment 1•8 years ago
|
||
And of course maybe it's ok to change behavior here given lack of interop. But we should do that consciously...
Updated•8 years ago
|
Priority: -- → P3
Comment 2•8 years ago
|
||
Bumping priority given bug 1362914.
Priority: P3 → P2
Summary: stylo: verify that shorthand serialization matches Gecko → stylo: shorthand serialization doesn't match Gecko
Updated•7 years ago
|
Assignee: nobody → kuoe0
Updated•7 years ago
|
Priority: P2 → --
Reporter | ||
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Comment 3•7 years ago
|
||
I have a patch that fixes this particular testcase but breaks some others. I'm going to take a look at how Gecko's implementation compares to the CSS spec.
Assignee: kuoe0 → josh
Assignee | ||
Comment 4•7 years ago
|
||
Submitted https://github.com/servo/servo/pull/18352 to fix this; try run at https://treeherder.mozilla.org/#/jobs?repo=try&revision=ef4cb7a57352b162e5fa1da0467d07f3d9eaec12.
Assignee | ||
Comment 6•7 years ago
|
||
Newest try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=6da6d7ff309b88f7646c8114f921c36ba8057ef3
Just waiting on review now. I think the changes should be uncontroversial.
Flags: needinfo?(josh)
Assignee | ||
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
status-firefox57:
--- → fixed
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•