Closed
Bug 1713551
Opened 3 years ago
Closed 3 years ago
Don't reserve MSAA id bits for the content process when the cache is enabled
Categories
(Core :: Disability Access APIs, task)
Tracking
()
RESOLVED
FIXED
91 Branch
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
Attachments
(1 file)
When the cache is enabled, we don't need to differentiate MSAA ids based on the originating process. This means we can (and should) use all bits for the unique id.
|
Assignee | |
Comment 1•3 years ago
|
||
Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/19e8b907fb7e When the cache is enabled, use all bits of the MSAA id for the object unique id. r=morgan
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•