Open
Bug 1189151
Opened 9 years ago
Updated 4 years ago
Link target tip may cover the link itself if reached by using TAB
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
NEW
People
(Reporter: rumbata, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150630154324
Steps to reproduce:
If a page is taller than the screen can show (i.e. has vertical scroll bars) and also has links in the lower part that are not initially visible, pressing the TAB key to jump from one link to the next will eventually reach a link that is at the bottom left of the visible area or below that. If the link is close to the left side of the window and if the status panel showing the link target is long enough, the status panel will fully or partially cover the link itself.
Actual results:
I am running the latest stable version and I was able to reproduce it in my daily profile, in a new profile as well as in the latest Aurora.
This is much similar to bug 631270 (https://bugzilla.mozilla.org/show_bug.cgi?id=631270), only in this case I am reaching the content by using TAB instead of the search function.
Expected results:
The status panel should show-up in another part of the window or the page should automatically scroll up so that the link and the status panel do not overlap.
Comment 1•9 years ago
|
||
Possible duplicate of bug 631280, though its STR involves enabling caret browsing.
Blocks: 541656
Component: Untriaged → General
Reporter | ||
Comment 2•9 years ago
|
||
I am not sure if it matters, but don't have caret browsing enabled.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Probably, "if focused" instead of "if reached by using TAB", because I get the same result
if link is focused via findbar (pressing Enter while text field in findbar is focused).
Updated•4 years ago
|
Component: General → Tabbed Browser
Updated•4 years ago
|
Severity: normal → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•