Open Bug 626919 Opened 12 years ago Updated 5 months ago

DIV with overflow-y:hidden is focusable

Categories

(Core :: DOM: Core & HTML, defect, P5)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

People

(Reporter: ic3b3rg, Unassigned)

References

Details

(Keywords: testcase) 

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9) Gecko/20100101 Firefox/4.0b9

An div element with overflow-y:hidden in its style is focusable

Reproducible: Always

Steps to Reproduce:
<html>
<body>
<input>
<div style="overflow-y:hidden"></div>
<input>
</body>
</html>

Actual Results:  
div is focusable

Expected Results:  
div should not be focusable

inputs included in the html for clarity only
This is the second of my reported bugs that I am reclassifying as a blocker.  I am doing so because I feel that this bug is a major usability problem.  I hope that whoever reviews this reclassification will agree with me.

Note that when running the code, tab from the first input and you'll see that the div receives focus.  This makes absolutely no sense from a usability perspective.

I should note that IE, Chrome, Safari and Opera do not suffer from the bug.
Severity: major → blocker
Not a blocker. Only bugs that stop the development and testing process for 
Mozilla are blockers:

blocker 	Blocks development and/or testing work
critical 	crashes, loss of data, severe memory leak
major 	major loss of function
normal 	regular issue, some loss of functionality under specific circumstances
minor 	minor loss of function, or other problem where easy workaround is present
trivial 	cosmetic problem like misspelled words or misaligned text
enhancement  feature requests

Severity is defined objectively according to the standards of the project, and 
has nothing to do with the importance of a bug, but rather it's impact as it 
relates to the entire project and userbase.
Severity: blocker → normal
Keywords: testcase
This is a major issue for Accessibility User. The user have to tab unnecessarily through these DIVS and are confused with the behavior. Please consider this for resolution ASAP
There is a testcase in attachment 8643317 [details].

Neil, is this behavior intentional?
Status: UNCONFIRMED → NEW
Component: General → DOM
Ever confirmed: true
Flags: needinfo?(enndeakin)
OS: Windows 7 → All
Product: Firefox → Core
Hardware: x86_64 → All
Yes, any scrollable area that doesn't have both directions set to hidden is focusable so that keyboard-only users can scroll the content.
Flags: needinfo?(enndeakin)
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.