-
Notifications
You must be signed in to change notification settings - Fork 137
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 tab focus & keyboard enter event to DrillDown & ViewDrd #802
Merged
barmac
merged 17 commits into
bpmn-io:develop
from
BrianJVarley:feat/view-drd-and-drilldown-focus
Dec 7, 2023
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
693530c
ViewDrdComp: Add tabIndex and include focus outline styling, DrillDo…
BrianJVarley fa70258
DrillDown: remove tabIndex as overlay button will receive focus natively
BrianJVarley f349730
ViewDrdComp: remove tabindex attr. since button natively receives foc…
BrianJVarley 05e9dea
view-drd-button: remove custom focus style, now provided by button el…
BrianJVarley 5ea5a0d
clean up unused code in PR
BrianJVarley 3d772d3
fix: add type=button
barmac 146a9c9
DrillDown: Add blue background & white color styling to button elemen…
BrianJVarley 53af083
drilldown: remove unused css class
BrianJVarley c41fde6
dmn-js-drd.css: remove background color on drilldown button so Browse…
BrianJVarley 7ee24ff
dmn-js-drd.css: remove background color on drilldown button so Browse…
BrianJVarley 77c13cc
chore: improve colors
barmac d7522bb
fix: show outline for view-drd button
barmac 990a8d2
feat: display span for non-interactive
barmac 8937133
test: remove exclusive test
barmac ecc4f26
test: revert unnecessary change
barmac 35100ba
increase outline offset
barmac 539ad76
lol
barmac File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Working on fixing this test, at the moment overlayEl does return the button element, but the drillSpy is not called in test. After the ENTER key event has been triggered.
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.
I wasn't able to fix this test too. It looks like in Chrome the synthetic keyboard event for enter doesn't trigger "click" handler, but a trusted keyboard event does. So this won't work:
We could add an event handler for Enter (and also Space), or just trust in browser behavior, and leave it untested.
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.
Yeah seems fine to skip this test, as the browser will trigger the click event on a button element by default on ENTER key event.