Last Comment Bug 569340 - Fire state change when document becomes uneditable
: Fire state change when document becomes uneditable
Status: NEW
Product: Core
Classification: Components
Component: Disability Access APIs (show other bugs)
: unspecified
: All All
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: alexander :surkov
Depends on:
Blocks: eventa11y statea11y
  Show dependency treegraph
Reported: 2010-06-01 06:05 PDT by David Bolter [:davidb]
Modified: 2012-03-06 23:02 PST (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

manual test file (471 bytes, text/html)
2010-06-01 06:11 PDT, David Bolter [:davidb]
no flags Details

Description User image David Bolter [:davidb] 2010-06-01 06:05:46 PDT
Spin off from bug 564471. We fire a state change event when we receive an obs_documentCreated, which indicates that a document has become editable. We should fire and event when a document becomes uneditable.


Fires only one state change event currently -- for the "on".
Comment 1 User image David Bolter [:davidb] 2010-06-01 06:11:05 PDT
Created attachment 448511 [details]
manual test file

Running this with trunk on Windows, using accprobe, I see worrisome details about the accessible objects from the events. Worrisome states include 'defunct', and/or 'invalid' when turning designMode one and off. Possibly spin off bugs await.

Note You need to log in before you can comment on or make changes to this bug.