Closed Bug 516123 Opened 16 years ago Closed 15 years ago

Remove platform specifics from nsAccTextChangeEvent

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: davidb, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Alexander requested this follow up for bug 515685. For massive text node insertions or deletions (like what can happen during graphs.mozilla.org, or when someone pastes large amounts of text into a text area) we spend about 18% of our time calculating the modified text in the constructor of our text event. We felt this made 515685 worth taking. This text change event is in our internal gecko accessibility layer, which should really be the same when compiled on each platforms. This is a design strategy and makes things easier for our automated tests and for gecko based AT. Hmmm, actually we should test Firevox to make sure it isn't broken!
Firevox should be unaffected.
So to fix this bug, ideally we will find a way to keep the performance improvement of bug 515685, and resolve our design transgression (see comment 1). I suppose we could subclass nsAccTextChangeEvent in our windows layer.
not valid anymore, they were removed in Gecko 2.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.