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".
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.