New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Lock focus-mode: #8716
Comments
I'd have thought that the place for this sort of thing is the settings for
focus mode where you can already set it to be auto or not auto focus mode.
Some tweaks to the logic and another checkbox could be introduced.
I'm still not really clear how this is supposed to help magnification users
though, as if you set focus mode to auto as I have it it slips into it when
an interactive control appears in focus.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
-----
|
Thank you for your immediate acknowledgement.
As further examples,
These browser characteristics work best in focus (pass-through) mode:
selecting text with the mouse (a feature that obviously necessitates
eyesight), page up/down. Firefox features such as "Search for text when you
start typing" necessitate pass-through.
Partially-sighted people can use the visual appearance of the screen to see
the layout and to navigate, using the screen reader for things like hover
echo and reading selected-text.
That is why it would be great to lock pass-through mode.
Is there any way to get pass-through behavior without changing the NVDA
program?
Larry Silvermintz
Sarasota, FL
…_____
From: Brian Gaff [mailto:notifications@github.com]
Sent: Wednesday, September 05, 2018 3:35 AM
To: nvaccess/nvda
Cc: LarrySilvermintz; Author
Subject: Re: [nvaccess/nvda] Feature request: Lock focus-mode: (#8716)
I'd have thought that the place for this sort of thing is the settings for
focus mode where you can already set it to be auto or not auto focus mode.
Some tweaks to the logic and another checkbox could be introduced.
I'm still not really clear how this is supposed to help magnification users
though, as if you set focus mode to auto as I have it it slips into it when
an interactive control appears in focus.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
-----
-
You are receiving this because you authored the thread.
Reply to this email directly, view
<#8716 (comment)> it on
GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/AXygU_3QAbyiJhX56eQ_s2taq
UlO-ty2ks5uX36MgaJpZM4WZ2AV> the thread.
<https://github.com/notifications/beacon/AXygU5qjtM4VKpJ9KuSDcXUnAgm8FX_Fks5
uX36MgaJpZM4WZ2AV.gif>
|
Yep, a separate checkbox in the Browse Mode NVDA Settings in combination with a trigger profile could solve this issue. Furthermore it should be possible – even when NVDA is running – to scroll the website up and down via the arrow keys and via PGUP/PGDN while focus mode is on. |
Thank you Daniel!
I�m so glad you see the value of my request and perhaps will help to
implement it.
Cheers!
Larry Silvermintz
Sarasota, FL
…_____
From: Daniel Mayr [mailto:notifications@github.com]
Sent: Thursday, September 06, 2018 7:25 AM
To: nvaccess/nvda
Cc: LarrySilvermintz; Author
Subject: Re: [nvaccess/nvda] Feature request: Lock focus-mode: (#8716)
Yep, a separate checkbox in the Browse Mode NVDA Settings in combination
with a trigger profile could solve this issue. Furthermore it should be
possible þ even when NVDA is running � to scroll the website up and down via
the arrow keys and PGUP/PGDN while focus mode is on.
�
You are receiving this because you authored the thread.
Reply to this email directly, view
<#8716 (comment)> it on
GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/AXygU0uB_z-PLAeMI4C5tnS8w
0FCCEjBks5uYQX7gaJpZM4WZ2AV> the thread.
<https://github.com/notifications/beacon/AXygUweTzgyR-EoRWIjZnvi9-CCJVe3dks5
uYQX7gaJpZM4WZ2AV.gif>
|
At @BabbageCom, we also see the impmortance of this feature. Therefore, I will take this. |
Great!
Thank you so much!
Regards,
Larry Silvermintz
…_____
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Saturday, September 08, 2018 1:28 PM
To: nvaccess/nvda
Cc: LarrySilvermintz; Author
Subject: Re: [nvaccess/nvda] Feature request: Lock focus-mode: (#8716)
At @BabbageCom <https://github.com/BabbageCom> , we also see the
impmortance of this feature. Therefore, I will take this.
-
You are receiving this because you authored the thread.
Reply to this email directly, view
<#8716 (comment)> it on
GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/AXygU_tqbQd2ZmX3-nfu5DI9a
yKSDGMnks5uY_4ZgaJpZM4WZ2AV> the thread.
<https://github.com/notifications/beacon/AXygUyOasbIORP6oUpU1mf4A1LQqSgusks5
uY_4ZgaJpZM4WZ2AV.gif>
|
I've almost got it settled, however there is one thing I'd really like to implement. When someone explicitly disabled browse mode (i.e. enabled pass through), I'd like NVDA to remember that decision. So for example:
Since the user explicitly disabled browse mode here, it makes sense to remember that state. However, pass through is now remembered on a per tree interceptor basis, and since a new page load creates a new tree interceptor, the initial pass through mode gets lost. @jcsteh or @michaelDCurran: Any idea how to address this? May be we should get rid of browseMode.reportPassThrough.last while at it, that is, it should no longer be a property on the reportPassThrough method. |
That's the right idea! Thank you.
…_____
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Tuesday, September 11, 2018 10:01 AM
To: nvaccess/nvda
Cc: LarrySilvermintz; Author
Subject: Re: [nvaccess/nvda] Feature request: Lock focus-mode: (#8716)
I've almost got it settled, however there is one thing I'd really like to
implement. When someone explicitly disabled browse mode (i.e. enabled pass
through), I'd like NVDA to remember that decision. So for example:
1. Open google.com
2. Focus the edit box with browse mode
3. Press NVDA+space
4. Enter a search term and press enter.
Since the user explicitly disabled browse mode here, it makes sense to
remember that state. However, pass through is now remembered on a per tree
interceptor basis, and since a new page load creates a new tree interceptor,
the initial pass through mode gets lost.
@jcsteh <https://github.com/jcsteh> or @michaelDCurran
<https://github.com/michaelDCurran> : Any idea how to address this? May be
we should get rid of browseMode.reportPassThrough.last while at it, that is,
it should no longer be a property on the reportPassThrough method.
-
You are receiving this because you authored the thread.
Reply to this email directly, view
<#8716 (comment)> it on
GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/AXygUx56-PMSLHozLuq3d2NIp
Yxl6dtVks5uZ8IjgaJpZM4WZ2AV> the thread.
<https://github.com/notifications/beacon/AXygU3PtgZhvlcIkz3m9iESko-yhGkQNks5
uZ8IjgaJpZM4WZ2AV.gif>
|
Hi, I'm reopening this due to regression caused by the associated pull request in Microsoft Word. Thanks. |
Thank you Joseph. Would be good to get the feature.
Regards,
Larry Silvermintz
941-556-9200
Sarasota, FL
…_____
From: Joseph Lee [mailto:notifications@github.com]
Sent: Friday, March 29, 2019 3:41 PM
To: nvaccess/nvda
Cc: LarrySilvermintz; Author
Subject: Re: [nvaccess/nvda] Feature request: Lock focus-mode: (#8716)
Reopened #8716 <#8716> .
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on
<#8716 (comment)> GitHub, or
mute
<https://github.com/notifications/unsubscribe-auth/AXygUzRoZTEdA8FJmFGZg9NMH
RrKV_33ks5vbmxigaJpZM4WZ2AV> the thread.
<https://github.com/notifications/beacon/AXygU4MevboT-Ttu43xSKz6ylWW4-gKcks5
vbmxigaJpZM4WZ2AV.gif>
|
Overview: It is sometimes preferred to default to interacting with the Web in focus mode. For example, partially-sighted people using a magnifier with NVDA may prefer to start in, and stay in Focus Mode.
Therefore, the locked-focus setting would maintain focus-mode even when opening new browser windows, restarting the browser or possibly even when switching browsers.
First, please create a key command to lock focus mode, default could be NVDA+ctrl+space.
Second: Please create a configuration file setting to lock focus mode, The user could place this in either a global or a triggered-configuration.
The text was updated successfully, but these errors were encountered: