Joanmarie Diggs Reporter
	Description • 9 years ago

Steps to reproduce:
1. Launch the attached accessible event listener in a terminal
2. Launch Nightly, enable caret-navigation (F7)
3. Tab around document content (I used google.com)

Expected results: All accessible events would be emitted by an application with the accessible name of "Firefox"

Actual results: object:state-changed events are emitted by an application with the accessible name of "Firefox" BUT text-related events are emitted by an application with the accessible name of "Nightly". (It might extend beyond text-related events.)

Impact: Orca is getting all kinds of confused and ignoring events it should pay attention to and paying attention to events it should ignore because it no longer knows the events come from Firefox.

Regression introduced: The bug is not present on 23 May 2015 nightlies and earlier. Looks like it happened on the 24th.

	Joanmarie Diggs Reporter
	Comment 1 • 9 years ago

Sample output:

[application | Nightly] object:text-caret-moved [combo box | Search]
[application | Nightly] object:text-caret-moved [push button | Google Search]
[application | Firefox] object:state-changed:enabled [push button | Paste]
[application | Firefox] object:state-changed:sensitive [push button | Paste]
[application | Firefox] object:state-changed:focused [document frame | Google]
[application | Nightly] object:text-changed:delete:system [section | ]
[application | Nightly] object:text-changed:insert:system [section | ]
[application | Nightly] object:text-caret-moved [section | ]
[application | Firefox] object:state-changed:focused [document frame | Google]
[application | Firefox] object:state-changed:focused [push button | ]
[application | Firefox] object:state-changed:focused [push button | I'm Feeling Wonderful]
[application | Nightly] object:text-changed:delete:system [section | ]
[application | Nightly] object:text-changed:insert [section | ]
[application | Firefox] object:state-changed:active [frame | Google - Nightly]

	José Vilmar Estácio de Souza
	Comment 2 • 9 years ago

I can confirm that the problem appeared in 24 may.
I allways update nightly.

	Joanmarie Diggs Reporter
	Comment 3 • 9 years ago

Note that the above issue is present in builds prior to the 24th if the following preference is absent:
user_pref("browser.tabs.remote.autostart.disabled-because-using-a11y", true);

	Joanmarie Diggs Reporter
	Comment 4 • 9 years ago

I'm not sure if the bug was fixed, or if a preference needed to be re-toggled. But in nightly, I went into Edit->Preferences and unchecked 'Enable multi-process Nightly' and restarted Nightly. Now I can no longer reproduce the bug. Thanks Trev!!

José can you confirm Nightly works for you?

	José Vilmar Estácio de Souza
	Comment 5 • 9 years ago

(In reply to Joanmarie Diggs from comment #4)
> 
> José can you confirm Nightly works for you?

Yes it works after I unchecked 'Enable multi-process Nightly'.

	Joanmarie Diggs Reporter
	Comment 6 • 9 years ago

Thanks. I'm going to close this as WFM then.