Skip to content
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

spyder accessiblity for visualy impaired user with windows magnification tool - lens does follow-up the cursor or the mousse #21620

Open
10 tasks
FrancoisLB opened this issue Dec 15, 2023 · 4 comments

Comments

@FrancoisLB
Copy link

FrancoisLB commented Dec 15, 2023

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

once spyder is opened in anaconda/spyder, the windows magnification tool is not able to follow-up the focus when moving the caret of the mousse in the opened python code in the editor panl.

What steps reproduce the problem?

eacht time a python code is opened in the spyder editor

  1. open a python code
  2. clic in the editor
  3. move the text cursor when the magification tool is active. the lens does not fooow-up the cursor

What is the expected output? What do you see instead?

in the edition panel, the magnification tool of windows is supposed to follow-up the text cursor or the mousse.

Paste Traceback/Error Below (if applicable)

not applicable 

PASTE TRACEBACK HERE

Versions

=> spyder integrated to Anaconda Spyder 2023 -09

  • Spyder version:
  • Python version: 3.11.0
  • Qt version:
  • PyQt version:
  • Operating System name/version: windows 11

Dependencies

PASTE DEPENDENCIES HERE
@ccordoba12
Copy link
Member

Hey @FrancoisLB, thanks for reporting. We'll try to take a look at this issue in Spyder 6, to be released next year.

@dalthviz, are you able reproduce this problem?

@dalthviz
Copy link
Member

I think I was able to reproduce this. From a quick check, seems like positioning the cursor over a line in the Editor which is being displayed at the screen bottom makes the focus jump to top of the Editor 🤔 Also if you activate the read functionality seems like the focus goes to the top of the file:

image

In the screenshot above, you can see the reader cursor not fully following the actual Editor cursor position (it follows the horizontal position only while showing some sort of vertical offset?

Also, just in case checked with the IPython Console and seems like there the magnification tool reader works correctly:

image

@FrancoisLB
Copy link
Author

Hello,

i do confirm your diagnostic. that's exactly the observed behavior.

i observed this situation in spyder since about 1 to 2 years.

in the edit panel, this anomaly is also visible with a screen reader such as NVDA (Non Visual Desktop Access). NVDA is a free and open source tool developped by NV Access (the Australian Fondation).

when the text cursor is mouved in the code by pressing up and down arrow keys, NVDA does not annonce the text correctly. it's probabily due to an anomaly with the focus management.

many thanks for your help.

best regards

François

@dalthviz
Copy link
Member

Thank you for the info @FrancoisLB ! We will try to see if we can fix this in a future Spyder release so that's why we will keep the issue open 👍

@ccordoba12 ccordoba12 modified the milestones: v6.0.1, v6.0.2 Sep 6, 2024
@ccordoba12 ccordoba12 modified the milestones: v6.0.2, v6.x.x Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants