-
Notifications
You must be signed in to change notification settings - Fork 49
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
Keyboard shortcuts for 'Accept/Revert url/test' buttons #360
Keyboard shortcuts for 'Accept/Revert url/test' buttons #360
Conversation
@@ -60,14 +62,16 @@ define(['angularAMD', 'userSettingsService'], function (angularAMD) { | |||
}, | |||
'221': function () { | |||
scope.traverseTree('down'); | |||
} | |||
}, | |||
'65': accept, |
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.
Great job!
What do you think, maybe we could remember ASCII codes in variables instead of add 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.
Actually we don't need to use ASCII codes at all and we can use event.key property instead of event.keyCode which is returning single character that identify keyboard buttons. I added new shortcuts using existing convention. If it is necessarily I can quick refactor it.
@@ -3410,6 +3410,9 @@ It is possible to search tests and URLs by the query. Searched fields are the UR | |||
* use **[** / **]** to navigate between test's urls | |||
* press **m** to show/hide layout mask (when available) | |||
* press **←** / **→** to navigate between url's tabs | |||
* press **a** for accepting suite/test/url |
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.
Please update only SuiteReportFeatures.md
. I think that it isn't a good idea to update historical documentation ;)
} | ||
|
||
function accept(event) { | ||
clickButton('.button-blue', event); |
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.
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.
Assumption is that only buttons inside toolbar-bottom
or tab-content-toolbar
will be clicked (function clickButton is looking for those classes first and then looking in their child nodes proper buttons for click). "Save all changes" button is inside sidepanel
so it will not be clicked.
Added Ids for buttons for better identification
tested, working well ✔️ |
Description
Motivation and Context
#317
Screenshots (if appropriate):
Types of changes
Checklist:
I hereby agree to the terms of the AET Contributor License Agreement.