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

[full-ci] Keyboard navigation disable for inputs #7648

Merged
merged 4 commits into from
Sep 16, 2022

Conversation

lookacat
Copy link
Contributor

@lookacat lookacat commented Sep 16, 2022

Description

Disable keyboard navigation on textarea and input

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

@update-docs
Copy link

update-docs bot commented Sep 16, 2022

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@lookacat lookacat marked this pull request as ready for review September 16, 2022 10:21
@lookacat lookacat requested a review from kulmann September 16, 2022 10:50
@ownclouders
Copy link
Contributor

Results for oCISSharingBasic https://drone.owncloud.com/owncloud/web/28384/54/1

💥 The acceptance tests failed on retry. Please find the screenshots inside ...

webUISharingAcceptShares-acceptShares_feature-L228.png

webUISharingAcceptShares-acceptShares_feature-L228.png

💥 The oCISSharingBasic tests pipeline failed. The build has been cancelled.

Copy link
Contributor

@AlexAndBear AlexAndBear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one objection, but personal style I guess

@@ -86,6 +86,8 @@ export default defineComponent({
}),

areCustomKeyBindingsEnabled() {
const activeElementTag = document.activeElement.tagName
if (['textarea', 'input', 'select'].includes(activeElementTag.toLowerCase())) return true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally not a fan of the inline return without {}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same. Code style in web and related repos is to not inline return statements.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried to find a eslint rule set plugin, but nothing found unfortantly

@lookacat lookacat changed the title Keyboard navigation disable for inputs [full-ci] Keyboard navigation disable for inputs Sep 16, 2022
@lookacat lookacat force-pushed the keyboard-navigation-disable-for-inputs branch from ba505a6 to 3a180b5 Compare September 16, 2022 11:14
@sonarcloud
Copy link

sonarcloud bot commented Sep 16, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@lookacat lookacat merged commit c074c0d into master Sep 16, 2022
@delete-merged-branch delete-merged-branch bot deleted the keyboard-navigation-disable-for-inputs branch September 16, 2022 14:15
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.

4 participants