Closed
Bug 1365163
Opened 7 years ago
Closed 7 years ago
Remove the layout.css.display-flow-root.enabled preference
Categories
(Core :: CSS Parsing and Computation, enhancement, P2)
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: mbrubeck)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
stylo seems to not support this.
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•7 years ago
|
||
Alternately, should we remove this pref before Stylo ships? It was added in bug 1322191 and has been enabled by default since Firefox 53.0.
Reporter | ||
Comment 2•7 years ago
|
||
If we're pretty sure that we won't have to emergency-disable this thing, we could remove the pref... I suspect that might be ok.
Flags: needinfo?(mats)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → mbrubeck
Assignee | ||
Comment 4•7 years ago
|
||
Patch to remove the pref: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f69abef2157f02548bd63ffbd493b8ab6a9cebec As mentioned in bug 1366914, there are still some remaining prefs in nsLayoutUtils.cpp that we will need to deal with eventually.
Status: NEW → ASSIGNED
Summary: stylo: Need to support the layout.css.display-flow-root.enabled preference → Remove the layout.css.display-flow-root.enabled preference
Comment hidden (mozreview-request) |
Comment 6•7 years ago
|
||
mozreview-review |
Comment on attachment 8874875 [details] Bug 1365163 - Remove pref layout.css.display-flow-root.enabled. https://reviewboard.mozilla.org/r/146256/#review150230
Attachment #8874875 -
Flags: review?(mats) → review+
Pushed by mbrubeck@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1a313acd4110 Remove pref layout.css.display-flow-root.enabled. r=mats
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1a313acd4110
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•