Re: [orca-list] slack probably inaccessible, maybe something happened in firefox 57?

[Jude DaShiell <jdashiel panix com>]

Please remember computer memory is like batteries.  Eventually it's 
permanently used up then it's time to buy a new computer.  Also, memory 
has bad spots in it.  This may mean use of the computer with errors like 
these where the computer burned through a bad spot in the memory.  Once 
burned through, that spot and defect is gone permanently.  This is one of 
the causes of what are described as glitches and they effect everything 
that runs on memory sooner or later.



--

Seems this bug is launch specific and does not happen now at all, so not
sure if I actually have *any* way to reproduce

W dniu 21.11.2017 o 17:31, Alex ARNAUD pisze:
> OK, I understand. You can disable the new feature multiprocessing if it
> breaks your usage
>
>  Before that, could you tell us what bug do you have encounter inside
> Slack? What is your Orca version? It could be important to fix the issue
> for the future.
>
> The steps are :
> 1) Open Firefox
> 2) Open about:config from the URL
> 3) In the search field type : "browser.tabs.remote.autostart.2"
> 4) Tab one time and check the value, if the value is true, do the step 5
> 5) Press the menu key to see the contextual menu and choose inverse value
> 6)  Restart Firefox
>
> Best regards.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org