386027 - No state changed event for STATE_EDITABLE when MIDAS is set to readonly

Status: RESOLVED INCOMPLETE

(Core :: Disability Access APIs, defect)

Description

[Ginn Chen]

Try http://www.mozilla.org/editor/midasdemo/

Mark "Readonly" checkbox.

Check with accerciser.

Comment 1

[Ginn Chen]

185     editor->GetFlags(&flags);
186     if (0 == (flags & nsIPlaintextEditor::eEditorReadonlyMask)) {
187       *aExtraState |= nsIAccessibleStates::EXT_STATE_EDITABLE;
188     }

should be copied/moved to nsDocAccessible.cpp

We need a general fix for EXT_STATE_EDITABLE and STATE_READONLY.

Comment 2

[Aaron Leventhal]

Bug 390767 fixes the state but we need to keep this open for the STATE_EDITABLE state change event.

Comment 3

[Aaron Leventhal]

Here's the code in the testcase which switches the rich text area to readonly:

It does that via
document.getElementById('edit').contentWindow.document.execCommand("readonly",
false, !(source));  

I'm not sure how we can detect that.

Comment 4

[[e-mail]]

It's worse for chrome; making an editor readonly is as simple as
editor.flags |= nsIPlaintextEditorMail.eEditorReadonlyMask;

So you would need to update nsEditor.cpp to dispatch some sort of event.

Comment 5

[alexander :surkov (:asurkov)]

Fire an event from nsTextEditRules::SetFlags(), so we get events for plaintext and html editors and it looks it's all sort of editors mozilla uses. Then catch event in ally and fire state changed events. Though then we don't need to fire state changed events based on attribute changing to avoid 
dublication. Though how can we fire an event from nsTextEditRules::SetFlags(), should be the event sync or async?

Comment 6

[Aaron Leventhal]

Surkov, this isn't a priority for Firefox 3.

Comment 7

[alexander :surkov (:asurkov)]

(In reply to comment #2)
> Bug 390767 fixes the state but we need to keep this open for the STATE_EDITABLE
> state change event.

still a problem

Comment 8

[David Bolter [:davidb] (NeedInfo me for attention)]

AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.