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.

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

Add new Tabbing stragety for root blocks. #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Agapanthus
Copy link
Owner

By default, MathQuill allows the browser to handle Tab in the standard way
when the cursor is in the root block. This means that the user will move to
the next focusable element in tab order. This behavior bypasses any templates
between the current cursor position and the end.

If templates are thought of as editable areas, like mini-textfields, this
approach feels unexpected to keyboard users, who would expect 'focus' to
traverse to the next 'field,' i.e. next template.

This commit adds a new configuration property: tabAction. By default tabAction
simply uses the current behavior. Users can specify a value of
'escapeAndTemplate' to allow Tabs from the root block to find the next template
or to move outside of the MathQuill field if no templates exist.

By default, MathQuill allows the browser to handle Tab in the standard way
when the cursor is in the root block.  This means that the user will move to
the next focusable element in tab order.  This behavior bypasses any templates
between the current cursor position and the end.

If templates are thought of as editable areas, like mini-textfields, this
approach feels unexpected to keyboard users, who would expect 'focus' to
traverse to the next 'field,' i.e. next template.

This commit adds a new configuration property: tabAction.  By default tabAction
simply uses the current behavior.  Users can specify a value of
'escapeAndTemplate' to allow Tabs from the root block to find the next template
or to move outside of the MathQuill field if no templates exist.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants