Disable "auto-focus" in screen magnifier

Hi list,

Not sure why that's a bug. Anyway, if you think that it is a bug, and
want to elaborate, you can create a new bug following this link:

https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-shell
(component magnifier)

> OK, i will report what i think is a bug when i get the time.
Please do. It is really useful to learn about any problems people might
be experiencing when they use the magnifier since 3,10. Feel free to
take a look at some of the magnifier bugs already listed too if you get
a chance.
>>> So, is there any way to disable this "auto-focus" feature?
>> We are still working on a UI to configure it (this is a know bug, and
>> hopefully will be solved on next stable release). But you can disable
>> tracking writing the following command on a terminal:
>>
>> gsettings set 'org.gnome.desktop.a11y.magnifier' 'focus-tracking' none
>> gsettings set 'org.gnome.desktop.a11y.magnifier' 'caret-tracking' none
>>
> Thanks
I hold my hand up to this (sorry Alejandro, I had not yet read through
your post the first time around when I answered this thread so I had
missed that)

The reason the ui implementation is not in yet is probably because I
have not done it and, (sorry, but...)  the reason I have not done this,
is because I aim to see to it that current problems I have found are
fixed before adding settings to the gui essentially because I think the
current problems are significant enough to make them seem more urgent
than integrating f/c tracking into the ui.

That said, this thread has raised an important point that I may have
overlooked before so, I am not sure of the best way to proceed now. I
have no idea if others have already begun working on the ui since I put
it down, or not but (maybe wrong in) assuming nobody has done so here, I
think it may be useful if I indicate what I think the possibilities are
from my perspective, in the now:

1.  I could reset the defaults for focus and caret tracking to 'none' by
default and attach the patch to a bug until the issues I am working on
have made progress.

2. I could put resume with control center ui and submit a patch so the
feature is complete albeit a bit buggier than when it was when it
landed.(note: I have no idea what the design team are currently cooking
up for g-c-c as I say this but last time I checked, I got the impression
they would be taking the lead on deciding what goes where etc - more
than happy to let them do their thing but suspect I would need to find
out what it is to make the f/c settings work underneath :-))

3. The ui is under control or otherwise and I carry on as before.

As always, I am happy be guided by well reasoned advice, comments and/or
suggestions about this work either on this list or IRC and I hope that
this has been able to clarify.

Regards,
Magdalen