Open Bug 1974383 Opened 3 months ago Updated 7 days ago

Implement `headingoffset` attribute

Categories

(Core :: DOM: Core & HTML, enhancement)

enhancement

Tracking

()

ASSIGNED
Size Estimate S
Tracking Status
firefox142 --- affected

People

(Reporter: keithamus, Assigned: keithamus)

References

()

Details

(Keywords: dev-doc-needed)

Attachments

(1 file)

This is a tracking issue for implementing the proposed headingoffset attribute as discussed in https://github.com/whatwg/html/issues/5033. There is a draft spec: https://github.com/whatwg/html/pull/11086

See Also: → 1974386

Just a heads up that this will require accessibility engine changes at multiple layers. The most obvious place is here. However, because this method is in the Accessible base class and must thus work for both local and remote Accessibles, some mechanism will need to be added to get the offset, and that will need to be pushed from content to parent and included in the RemoteAccessible cache.

(In reply to James Teh [:Jamie] from comment #1)

Just a heads up that this will require accessibility engine changes at multiple layers. The most obvious place is here. However, because this method is in the Accessible base class and must thus work for both local and remote Accessibles, some mechanism will need to be added to get the offset, and that will need to be pushed from content to parent and included in the RemoteAccessible cache.

Thanks for this! For RemoteAccessible I was looking to put the level as a CacheKey of mCachedFields, but I am happy to take suggestions for alternative/better ways to handle this.

Keywords: dev-doc-needed
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: