The Windows7 Magnifier allow to magnify a part of the screen. An option allows the magnifier to automatically follow the insertion point.
The magnifier follows perfectly the insertion point when using most of software applications (Wordpad, Notepad, Microsoft Word, Notepad++ , Thunderbird, Firefox.
But NOT with LibreOffice Writer !!!! With LibreOffice, the magnifier follows only the mouse pointer.
This problem makes LibreOffice not usable for persons with visual impairment.
Seen on Windows7 and on Windows Vista, both with LibreOffice 3.3.2
Please, do you know where is a description of the API that makes this possible? I suppose the application has to let the system know where exactly is the cursor...
Still seeing this with LibO 3.3.3 (OOO330m19 (Build:301)) on Windows 7 (X64). If there is anything that I can do or sort out, please let me know! This issue is blocking me from switching to LibO. Thanks!!
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
The problem is still here with LibreOffice 3.5.0 Beta 1 on Windows Vista
NEW, unassigned bug: replace "infoprovider" with move to state "NEEDINFO".
needinfo keyword redundant by needinfo status.
Windows specific problem. Please, take look at this when have time
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.
Still seeing this with LibO 184.108.40.206 (Build-id: e29a214) on Windows 7 (X64). If there is anything that I can do or sort out, please let me know! This issue is blocking me from switching to LibO due to my dependence on low vision aids. Thanks!!
I have taken the following additional steps, but that didn't help:
1. Downloaded and installed Oracle JRE 1.7.0_07 (32 bit) from http://java.com
2. Enabled the Java Access Bridge following: http://docs.oracle.com/javase/7/docs/technotes/guides/access/enable_and_test.html
3. Added and selected the new JRE in LibO: Options > Java
4. Enabled assistive technology support in LibO: Options > Accessibliity
5. Restarted LibO.
Any other suggestions?
Windows 7 "Ease of Access" Magnifier feature is a Microsoft UI Automation dependent Assistive Technology with Aero dependencies for Full Screen & Lens modes that can only follow the mouse input or respond to cursor controlled positioning.
Tracking keyboard focus or text insertion point options are implemented only in the Magnifier's Docked mode.
It is a very helpful AT implementation, but Microsoft UI Automation can not follow Java Accessibility API focus events so existing mapping of UNO Accessibility API bridge events via Java Access Bridge (JAB) is not supported by Magnifier.
As a native Windows bridge is implemented with IAccessibile2, availibility of IAccessibleEditableText should expose position information to UI Automation for Magnifier.
Setting as Enhancement that should resolve with work on IAccessibile2 bug 39956
The issue is still present in 220.127.116.11. I think V. Stuart Foote is right when he says that it is related to the Java Accessibility API and that IAccessible2 needs to be implemented before this issue can be fixed. (Windows 7 Magnifier also fails to follow the text insertion point in NetBeans, which AFAIK, also implements the Java Accessibility API.)
Should bug 39956 be marked as a blocker for this one?
Anyway, a description of steps to reproduce the issue is missing.
1. Start the Windows 7 Magnifier (press the Windows key and type "Magnifier").
2. In the Magnifier options, uncheck "Follow the mouse pointer" and "Follow the keyboard focus" but make sure that "Have Magnifier follow the text insertion point" is checked.
3. Create, e.g., a Writer document and start typing text. Notice that the caret in the Magnifier window does not stay in the middle but eventually moves out of that Window. (Compare this behaviour with e.g. Notepad or a comment field on a webpage displayed in Firefox.)
4. In the Magnifier options, "Follow the keyboard focus" and notice that the behaviour does not improve.
Desired behaviour: the caret remains in the middle of the (docked) Magnifier window; compare with behaviour in e.g. Notepad.
As mentioned before, this test needs to be repeated once the IAccessible2 code has replaced the Java Accessibility API.
To track the corresponding Apache OpenOffice issue: https://issues.apache.org/ooo/show_bug.cgi?id=117740
Looks like this was confirmed as an enhancement request. Moving to NEW as REOPENED is incorrect status.
I use Win 7 with the final patch and
Version: 18.104.22.168.beta1+ (x64)
Build ID: 94c217984e456196047ce41096d4a6f05bf66382
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-US
No, it doesn't seem fixed.
Tried today with Windows10 1909 64bits and LibreOffice 22.214.171.124
The magnifier still doesn't follow the insertion point.
No, it doesn't seem fixed with LibreOffice 7.0.0 too...
Tried today with Windows10 1909 64bits and LibreOffice 7.0.0 beta1 X86
The magnifier still doesn't follow the insertion point.
Created attachment 161479 [details]
Magnifier follows text insertion point, but only in Win 7
You're correct, it does not work with Win 10. I should have tested it before with Win 10. Because the original report referred to Win 7 I only tested it with my VM, which has Win 7.
But the magnifier following the text insert position DOES work in Win 7. Really, no kidding! I attached a video I made with VBox.
Windows10 didn't exist 9 years ago, when I posted the initial report...