Closed
Bug 507599
Opened 15 years ago
Closed 13 years ago
Deleting thousands of lines of text from a textarea emits many warnings
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: neil, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce problem: 1. Activate accessibility (e.g. via DOM Inspector) 2. Edit a really large Bugzilla attachment 3 [review]. Try to delete a few thousand lines Stack backtrace: nsTextAccessible::AppendTextTo nsAccUtils::TextLength nsHyperTextAccessible::DOMPointToHypertextOffset nsDocAccessible::CreateTextChangeEventForNode nsDocAccessible::InvalidateCacheSubtree nsAccessibilityService::InvalidateSubtreeFor nsGenericElement::doRemoveChildAt nsGenericElement::RemoveChildAt nsGenericElement::doRemoveChild nsGenericElement::RemoveChild nsGenericElement::RemoveChild DeleteElementTxn::DoTransaction EditAggregateTxn::DoTransaction The aggregate transaction consists (in my test case) of 7956 nodes of which half are <br> nodes and half are text nodes. For each of these nodes, DOMPointToHypertextOffset seems to scan the entire original text, including deleted nodes, which causes millions of warnings in nsTextAccessible::AppendTextTo as the frames are all null.
Updated•15 years ago
|
Comment 1•13 years ago
|
||
Neil, is this still valid?
Reporter | ||
Comment 2•13 years ago
|
||
Looks like something got rewritten along the way and the STR no longer work.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Comment 3•13 years ago
|
||
(In reply to neil@parkwaycc.co.uk from comment #2) > Looks like something got rewritten along the way and the STR no longer work. yeah, we handle that so differently after Firefox 4. Thanks for checking.
You need to log in
before you can comment on or make changes to this bug.
Description
•