Closed Bug 420721 Opened 16 years ago Closed 13 years ago

Crash related to manufacturing text change events

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: aaronlev, Unassigned)

Details

(Keywords: access, crash) 

I see several crash reports related to text change events we create after a timeout. It's puzzling.

Here are two slightly different versions of the crash:
http://crash-stats.mozilla.com/report/index/d4cef263-e825-11dc-ba41-001a4bd43ed6
and
http://crash-stats.mozilla.com/report/index/e2756205-e7b2-11dc-b235-001a4bd43ed6
Ginn, Evan, Alexander -- any ideas?
Possibly related to bug 420053.
Just question, could we fire new text event the same time when GetModifiedText() is called? Is it technically possible?
Alexander, can you explain your idea more? I don't understand it, and I also don't understand the crash. Do you know why it's crashing?
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
stacks aren't available anymore, no signature, closing as worksforme (bug 429648 might be related per comment #3)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.