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

Jump to bottom

Jumping to head after clicking in contents (Internet Explorer 11) #4134

Closed
nvaccessAuto opened this issue May 10, 2014 · 8 comments
Closed

Jumping to head after clicking in contents (Internet Explorer 11) #4134

nvaccessAuto opened this issue May 10, 2014 · 8 comments
Labels
bug feature/browse-mode
Milestone
2014.3

Comments

@nvaccessAuto
Copy link

Reported by The_Dark_Man on 2014-05-10 15:16
When I click in the contents of the User Guide or Wikipedia the screen jumps to the searched head, but when I click on the arrow-buttons, the cursor is on the top of the side and not on the searched head. I have this problem with Internet Explorer, only.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-05-11 02:20
Can you please clarify what you mean by the arrow buttons? Do you mean the Back and Forward buttons for the web browser itself or are you referring to some arrow buttons in the web page itself?

@nvaccessAuto
Copy link
Author

Comment 2 by The_Dark_Man on 2014-05-11 14:01
I mean the arrow keys on my keyboard. Try to work with the User guide with Internet Explorer 11. You will see the problem. I had this problem on two different computers.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2014-05-14 00:59
Confirmed. I was confused because you said it jumps to the heading when you activate the link, but I think you mean it jumps visually but NVDA doesn't jump.

Technical: This is another case of document.getElementById not behaving as it did previously. I'm not sure whether it's best to use document.getElementsByName or document.all.item.
Changes:
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 4 by The_Dark_Man on 2014-05-14 16:29
I hope somebody can correct this bug. Now, the problem is announced.

@nvaccessAuto
Copy link
Author

Comment 5 by Michael Curran <mick@... on 2014-05-15 00:52
In [b89c854]:

Merge branch 't4134' into next. Incubates #4134

Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

Comment 6 by Michael Curran <mick@... on 2014-05-15 03:17
In [d3931a3]:

Merge branch 't4134' into next. Incubates #4134

@nvaccessAuto
Copy link
Author

Comment 7 by Michael Curran <mick@... on 2014-06-10 04:33
In [6fe23e8]:

Merge branch 't4134'. Fixes #4134

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto
Copy link
Author

Comment 8 by mdcurran on 2014-06-10 04:35
Changes:
Milestone changed from next to 2014.3

@nvaccessAuto nvaccessAuto added this to the 2014.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug feature/browse-mode
Projects
None yet
Milestone
2014.3
Development

No branches or pull requests
1 participant
@nvaccessAuto