Closed
Bug 385444
Opened 17 years ago
Closed 17 years ago
Simplify code that decides whether to fire SHOW/HIDE/REORDER
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
(Keywords: access)
Attachments
(1 file)
Right now we have 3 case: 1) Do not fire SHOW/HIDE/REORDER (doc not loaded and no accessibles yet) 2) Fire them (doc is loaded) 3) Sometimes fire them (doc partially loaded and some accessibles created) We want to remove #3 because it makes the code larger and more confusing, and is an unncessary optimization. If there are any accessibles (other than the doc accessible) already created, lets just go ahead and fire SHOW/HIDE/REORDER.
Assignee | ||
Comment 1•17 years ago
|
||
Attachment #269358 -
Flags: review?(surkov.alexander)
Comment 2•17 years ago
|
||
Do we need GetAccessibleInParentChain() then? Can we merge it completely with GetParent()?
Assignee | ||
Comment 3•17 years ago
|
||
We need it, because it takes a DOM node which might not have an accessible.
Comment 4•17 years ago
|
||
Comment on attachment 269358 [details] [diff] [review] If content is not loaded and only doc accessible exists, exit early, otherwise run the full invalidation sequence r=me
Attachment #269358 -
Flags: review?(surkov.alexander) → review+
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•