Closed
Bug 1845744
Opened 2 years ago
Closed 2 years ago
Separate out selector-specific node flags
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
118 Branch
| Tracking | Status | |
|---|---|---|
| firefox118 | --- | fixed |
People
(Reporter: dshin, Assigned: dshin)
References
Details
Attachments
(1 file)
:has invalidation adds 4 new entries, which goes over the amount of available flags.
Migrate selector-related flags out into a 32-bit hole in nsINode (Which incurs a penalty on 32-bit systems, unfortunately :/).
|
Assignee | |
Updated•2 years ago
|
Severity: -- → S3
|
|
Assignee | |
Comment 1•2 years ago
|
||
Upcoming :has invalidation (Bug 1792501) requires 4 more flags, and we're out of space.
This change consumes the remaining 32-bit hole in nsINode to migrate selector-specific
node flags.
This has implications on 32-bit platforms, specifically on text nodes.
|
||
Updated•2 years ago
|
Assignee: nobody → dshin
Status: NEW → ASSIGNED
Pushed by dshin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3222a05683fe
Move selector-specific node flags to a separate field. r=emilio
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•