Last Comment Bug 309329 - Should not expose content in invisible views
: Should not expose content in invisible views
Status: RESOLVED FIXED
: access, fixed1.8, sec508
Product: Core
Classification: Components
Component: Disability Access APIs (show other bugs)
: Trunk
: x86 All
: -- major (vote)
: ---
Assigned To: Aaron Leventhal
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-20 08:37 PDT by Aaron Leventhal
Modified: 2005-09-21 13:21 PDT (History)
2 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Patch with whitespace changes: 1) Use unified check for XUL and HTML. 2) Check AreAncestorViewsVisible() before creating accessible (4.17 KB, patch)
2005-09-20 08:40 PDT, Aaron Leventhal
no flags Details | Diff | Splinter Review
Patch without whitespace changes: 1) Unified check for HTML and XUL visibility, 2) Check AreAncestorViewsVisible() before creating accessible (2.02 KB, patch)
2005-09-20 08:41 PDT, Aaron Leventhal
parente: review+
bzbarsky: superreview+
asa: approval1.8b5+
Details | Diff | Splinter Review

Description Aaron Leventhal 2005-09-20 08:37:49 PDT
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.
Comment 1 Aaron Leventhal 2005-09-20 08:40:15 PDT
Created attachment 196796 [details] [diff] [review]
Patch with whitespace changes: 1) Use unified check for XUL and HTML. 2) Check AreAncestorViewsVisible() before creating accessible
Comment 2 Aaron Leventhal 2005-09-20 08:41:58 PDT
Created attachment 196797 [details] [diff] [review]
Patch without whitespace changes: 1) Unified check for HTML and XUL visibility, 2) Check AreAncestorViewsVisible() before creating accessible

Note You need to log in before you can comment on or make changes to this bug.