Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

md-tabs captures navigation key strokes (alt+left / alt+right) #9161

Closed
jheijkoop opened this issue Jul 28, 2016 · 1 comment
Closed

md-tabs captures navigation key strokes (alt+left / alt+right) #9161

jheijkoop opened this issue Jul 28, 2016 · 1 comment
Labels
resolution: won't fix There are no resources to fix this issue, the priority is too low, or it doesn't align w/ MD spec.

Comments

@jheijkoop
Copy link

Actual Behavior:

  • What is the issue? *
    When I click on a tab of a <md-tabs> and then press alt+left to navigate back, instead the focus on the tabs moves left (similar for alt-right) Therefor grabbing the input, before it can be passed to the browser
  • What is the expected behavior?
    I expected to navigate in history, maybe only a cursor key without alt would result in the encountered behaviour, but not the combination of alt+left / alt-right

CodePen (or steps to reproduce the issue): *

  • CodePen Demo which shows your issue:
  • Details:

Angular Versions: *

  • Angular Version:
    "angular": "1.4.9",
  • Angular Material Version:
    "angular-material": "1.1.0-rc.5",

Additional Information:

  • Browser Type: *
    Chromium
  • Browser Version: *
    Version 51.0.2704.103 (64-bit)
  • OS: *
    4.5.4-tuxonice Raised buttons don't have shadows #1 SMP Thu Jun 9 23:46:36 CEST 2016 x86_64 Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz GenuineIntel GNU/Linux
  • Stack Traces:

Shortcut to create a new CodePen Demo.
Note: * indicates required information. Without this information, your issue may be auto-closed.

Do not modify the titles or questions. Simply add your responses to the ends of the questions.
Add more lines if needed.

@ThomasBurleson
Copy link
Contributor

Will not fix for ngM1.x

@ThomasBurleson ThomasBurleson added the resolution: won't fix There are no resources to fix this issue, the priority is too low, or it doesn't align w/ MD spec. label Aug 22, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolution: won't fix There are no resources to fix this issue, the priority is too low, or it doesn't align w/ MD spec.
Projects
None yet
Development

No branches or pull requests

2 participants