Should not expose content in invisible views

RESOLVED FIXED

Status

()

Core
Disability Access APIs
--
major
RESOLVED FIXED
12 years ago
12 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

({access, fixed1.8, sec508})

Trunk
x86
All
access, fixed1.8, sec508
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

12 years ago
We should not be creating accessibles inside invisible views.

Testcase:
Open Help -> Check for updates
Use accexplorer to look at accessible tree

Much content is exposed that is not visible from wizard pages that are not current.
(Assignee)

Comment 1

12 years ago
Created attachment 196796 [details] [diff] [review]
Patch with whitespace changes: 1) Use unified check for XUL and HTML. 2) Check AreAncestorViewsVisible() before creating accessible
(Assignee)

Comment 2

12 years ago
Created attachment 196797 [details] [diff] [review]
Patch without whitespace changes: 1) Unified check for HTML and XUL visibility, 2) Check AreAncestorViewsVisible() before creating accessible
Attachment #196797 - Flags: superreview?(bzbarsky)
Attachment #196797 - Flags: review?(parente)

Updated

12 years ago
Attachment #196797 - Flags: review?(parente) → review+

Updated

12 years ago
Attachment #196797 - Flags: superreview?(bzbarsky) → superreview+
(Assignee)

Updated

12 years ago
Attachment #196797 - Flags: approval1.8b5?
(Assignee)

Updated

12 years ago
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED

Updated

12 years ago
Attachment #196797 - Flags: approval1.8b5? → approval1.8b5+
(Assignee)

Updated

12 years ago
Keywords: fixed1.8
You need to log in before you can comment on or make changes to this bug.