Cache tag object attribute
Categories
(Core :: Disability Access APIs, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox97 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
(Whiteboard: [ctw-m0])
Attachments
(2 files)
JAWS ignores semantics altogether when rendering buffers unless the tag object attribute is present.
I'm not sure how to best handle object attributes yet. I don't think we want a separate cache domain for every object attribute. We also don't want to cache some of the calculated attributes; e.g. posinset and setsize.
Assignee | ||
Comment 1•3 years ago
|
||
I just realised tag will never change, so it only needs to be included in the initial push.
Assignee | ||
Comment 2•3 years ago
|
||
In the CTW meeting, we agreed that most (but perhaps not all) object attributes would be flattened into mCachedFields. We will try to group them into several larger cache domains; e.g. DOM attributes. For attributes like tag that never change, we can just push them for the initial push regardless of cache domain.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
The RemoteAccessibleBase implementation is a stub for now, but will be expanded in the next patch.
Assignee | ||
Comment 4•3 years ago
|
||
Comment 7•3 years ago
|
||
Backed out 2 changesets (Bug 1742915) for causing android bustages.
Backout link: https://hg.mozilla.org/integration/autoland/rev/0c2905f3085a
Push with failures, failure log.
Assignee | ||
Updated•3 years ago
|
Comment 9•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8644eb330d8a
https://hg.mozilla.org/mozilla-central/rev/de58fa2ed2d5
Description
•