Closed
Bug 1345702
Opened 8 years ago
Closed 7 years ago
remove support for <style scoped>
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 1444905
People
(Reporter: bholley, Unassigned)
References
Details
We will need some machinery to support XBL scoped stylesheets to make video controls work. That work is tracked in bug 1290276.
Once we have that, we also need to consider <style scoped>. There's discussion about removing it in bug 1291515, with people leaning to keep it. If we keep it, we'll need to implement it, which hopefully won't be too much work after bug 1290276 is done.
Reporter | ||
Comment 1•8 years ago
|
||
Over to Ting-Yu to work on alongside bug 1290276.
Assignee: nobody → tlin
Priority: P3 → P1
Comment 2•7 years ago
|
||
Since we decided to remove support for <style scoped>, morphing this bug into the removal. Bug 1291515 is for disabling it in content documents, so this one blocks stylo being used in chrome documents.
Assignee: tlin → nobody
Priority: P1 → --
Summary: stylo: Implement (or remove) <style scoped> → remove support for <style scoped>
Comment 3•7 years ago
|
||
Remove bug 1290276 from the block list because it doesn't affect removing <style scoped>.
No longer blocks: stylo-chrome
Updated•7 years ago
|
Blocks: stylo-chrome
No longer depends on: 1290276
Updated•7 years ago
|
Priority: -- → P3
Comment 4•7 years ago
|
||
There is no chrome document except about:reader using <style scoped> right now, and about:reader shouldn't block us from using stylo elsewhere. Move it to block stylo-everywhere instead.
Updated•7 years ago
|
No longer blocks: stylo-everywhere
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•