Open
Bug 851870
Opened 12 years ago
Updated 2 years ago
warn when chrome code clones a CSSStyleSheetInner
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: dbaron, Unassigned)
Details
(Keywords: memory-footprint, perf, Whiteboard: [MemShrink:P2])
We should probably have a warning when chrome code clones a CSSStyleSheetInner that is otherwise shared between prototype documents, so that we don't take the resulting memory and performance regressions (e.g., bug 851862 comment 1).
Updated•12 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 2•12 years ago
|
||
We should make sure it does not warn when modifying an inline style sheet that was created dynamically. Though it may not usually be best practice (and we don't currently do this in-product), the CSSOM is read-write, and there are legitimate cases to use it as such.
Reporter | ||
Comment 3•12 years ago
|
||
Probably yes, but only under certain conditions (minimally, chrome document with a XUL Prototype Document, style sheet is initially non-empty).
Flags: needinfo?(dbaron)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•