Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ITextEditProvider::GetActiveComposition and GetConversionTarget #1

Open
alexkeng opened this issue Feb 2, 2022 · 0 comments
Open

ITextEditProvider::GetActiveComposition and GetConversionTarget #1

alexkeng opened this issue Feb 2, 2022 · 0 comments
Assignees
@dandclark
Labels
enhancement New feature or request

Comments

@alexkeng
Copy link
Contributor

alexkeng commented Feb 2, 2022

ITextEditProvider::GetActiveComposition and GetConversionTarget are APIs that Windows provides to expose IME information for UI Automation. As of Feb 2022, these two APIs don't seem to be really used by popular screen readers like NVDA (no reference in the code base) or JAWS, however, it appears we have a gap in EditContext's API surface where browser vendors don't have a way to map these IME info (i.e. the ranges for active composition and conversion target, now stored in EditContext) to the DOM that authors created for the accessibility purpose. There doesn't seem to be an immediate impact but It would be great if EditContext can provide APIs to create the mapping (for the ranges) so the browser vendors can fully implement the TextEdit control pattern
@dandclark dandclark added the enhancement New feature or request label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dandclark dandclark

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dandclark @alexkeng