-
Notifications
You must be signed in to change notification settings - Fork 233
A11y virtual attached keyexplorers #683
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the attached property is no longer being populated, but is still used. Can you check that that is as intended?
| * @param {ExplorerMathDocument} document The current document. | ||
| */ | ||
| public attachExplorers(document: ExplorerMathDocument) { | ||
| this.attached = []; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this.attached is no longer created or populated, but it is still used elsewhere in the code (in rerender() and updateDocument()). Is that still correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
I've now also made the more restarting more robust on collapsed elements. This only works with the latest fixes I made to SRE today.
There's still a minor kink to work out: When a collapse is triggered with the mouse while the key explorers are deeper in the tree they effectively refocus on a node that is no longer there. But that is for 3.2 to work out.
the refocus does not y
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solved that problem now. I will make a small PR once this PR is merged.
dpvc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, looks good. I'll merge.
This takes care of item 1 in #561 (comment)
Original problem was that key explorers where added to a node when they were switched on and removed when switched off.
Since only the last explorer was supposed to stop propagation of the key events, if the order was messed up, propagation might be stopped too early. (E.g., switch on speech, braille, keyboard magnificatio. Then switch off braille and speech, and switch on speech: magnification works, speech does not).
Now key explorers are attached only once and retain an
attachedflag. This ensure that the order of the explorers remains the same.