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

Tooltips Bug in IE11 and Edge, tabIndex property #384

Open
cathysiller opened this issue Nov 20, 2018 · 3 comments
Open

Tooltips Bug in IE11 and Edge, tabIndex property #384

cathysiller opened this issue Nov 20, 2018 · 3 comments
Labels
BUG External Pertains to external code/binary

Comments

@cathysiller
Copy link
Contributor

cathysiller commented Nov 20, 2018

Describe the Bug

Tooltips gained some functionality to automatically update their control element to make it keyboard accessible. However, due to a bug with IE and Edge 12-17, the tabIndex property reports the incorrect value for elements without an explicit tabindex. (Microsoft Issue #4365703)
This seems to have been corrected in Edge 18 (slowly rolling out across Windows 10 machines), but has not been corrected in IE11.
Need to look into options for IE11 compatibility.
If in doubt, manually add a tabindex="0" to the control element.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Go to 'IE11/Edge(12-17)'
  2. Click on tabIndex in the inspect element
  3. See how tabIndex starts at '0' but should start at tabindex="1"

Expected behavior

For tabIndex to begin with tabindex="1"

Environment

Please complete the following information:

  • Browser: [IE11 and Edge 12-17]

Additional Context

Add any other context about the problem here.

@CITguy
Copy link
Contributor

CITguy commented Nov 20, 2018

additional context:

In v0.15.0-rc.0, <hx-tooltip> added functionality in an attempt to automatically update its control element to make it keyboard accessible. However, due to a bug with IE and Edge 12-17, the tabIndex property reports the incorrect value for elements without an explicit tabindex. (Microsoft Issue #4365703)

  • This seems to have been corrected in Edge 18 (slowly rolling out across Windows 10 machines)
  • This has not been corrected in IE11.

@CITguy CITguy added the External Pertains to external code/binary label Dec 3, 2018
@CITguy
Copy link
Contributor

CITguy commented Jan 8, 2019

I can confirm that Edge 18 has fixed the bug.

@CITguy CITguy added the BUG label Feb 28, 2019
@CITguy CITguy pinned this issue Apr 26, 2019
@CITguy
Copy link
Contributor

CITguy commented Dec 16, 2019

Nothing can be done to fix IE, but we should update documentation to make consumers aware of the issue.

@CITguy CITguy unpinned this issue Dec 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG External Pertains to external code/binary
Projects
None yet
Development

No branches or pull requests

2 participants