Closed
Bug 633483
Opened 15 years ago
Closed 15 years ago
don't update children of container for dependent content that has an accessible
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
mozilla2.0b12
People
(Reporter: surkov, Assigned: surkov)
Details
(Keywords: access, perf)
Attachments
(1 file)
|
1.28 KB,
patch
|
davidb
:
review+
davidb
:
approval2.0+
|
Details | Diff | Splinter Review |
We force accessible children update when dependent content is scheduled for accessible creation, we can skip an update if accessible was created for dependent content already. The example would be an insertion the following into DOM:
<div>
<label for="input">label</label>
<input id="input">
</div>
label accessible is created, dependent input content processing is scheduled, accessible for input is created, scheduled processing is performed, excess update happens.
Attachment #511697 -
Flags: review?(bolterbugz)
Attachment #511697 -
Flags: approval2.0?
|
||
Comment 1•15 years ago
|
||
Comment on attachment 511697 [details] [diff] [review]
patch
r+a=me... yeah, wow that was some wasted updating.
Attachment #511697 -
Flags: review?(bolterbugz)
Attachment #511697 -
Flags: review+
Attachment #511697 -
Flags: approval2.0?
Attachment #511697 -
Flags: approval2.0+
|
Assignee | |
Comment 2•15 years ago
|
||
landed on 2.0 (fx4b12) - http://hg.mozilla.org/mozilla-central/rev/5062cd0282a6
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b12
|
||
Comment 3•15 years ago
|
||
Is there a testcase that helps me verify this?
|
|
Assignee | |
Comment 4•15 years ago
|
||
(In reply to comment #3)
> Is there a testcase that helps me verify this?
I don't think so. We could try to measure a perf though.
You need to log in
before you can comment on or make changes to this bug.
Description
•