Text events broken in text fields -- effective 3/15/08

RESOLVED FIXED

Status

()

defect
--
critical
RESOLVED FIXED
12 years ago
12 years ago

People

(Reporter: aaronlev, Assigned: aaronlev)

Tracking

({access, regression})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Go to http://www.google.com
Use accevent to watch events
Type letters 
TEXT_INSERTED events after the first get errors like the following:

TEXT_INSERTED	 Name=[Error getting string:80070057 - The parameter is incorrect.] Role=[Error getting role:80070057 - The parameter is incorrect.] State=[Error getting state:80070057 - The parameter is incorrect.] Attribs@@= NewText=
Flags: blocking1.9?
Broken for the first time in March 15 builds.
Summary: Text events broken in text fields → Text events broken in text fields -- effective 3/15/08
Actually this was caused by security fix bug 401155. It's preventing a11y requests from being handled.
Attachment #310281 - Flags: superreview?(bzbarsky)
Attachment #310281 - Flags: superreview?
Attachment #310281 - Flags: review?(jonas)
Attachment #310281 - Flags: review?
*please* mark regressions as dependencies. Even if they are just suspected. It is very easy to loose track of them otherwise.
Blocks: 401155
Blocks: 423696
Comment on attachment 310281 [details] [diff] [review]
Let a11y events through even during script unsafe times -- they are coming from win32

Looks ok.
Attachment #310281 - Flags: superreview?(bzbarsky) → superreview+
So are you sure that this code won't end up firing any events that content code can catch?
No, there might be a case where content code can catch it, but this a11y event only is fired when a screen reader or similar AT is running. I'll look into that issue but we need to get the accessibility builds going again.
Actually for content code to catch it, it would require either require that:
1) A Windows executable caught an MSAA event and in-process used an IAccessible method to perform an action or focus a node
2) The content had privileges to look at accessibility interfaces and catch events that way
Comment on attachment 310281 [details] [diff] [review]
Let a11y events through even during script unsafe times -- they are coming from win32

So I take it that's a "no"? If so looks fine to me, other than change NS_WARNING to NS_ERROR as we do want to assert.
Attachment #310281 - Flags: review?(jonas) → review+
Attachment #310281 - Flags: review?
Attachment #310281 - Flags: approval1.9?
Attachment #310281 - Flags: review?
Attachment #310281 - Flags: approval1.9? → approval1.9+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.