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

after installing nvda next 14998 can not edit cells in excel #8146

Closed
fernando-jose-silva opened this Issue Apr 6, 2018 · 32 comments

Comments

Projects
None yet
@fernando-jose-silva
Copy link

fernando-jose-silva commented Apr 6, 2018

Steps to reproduce:

Install the nvda next 14998.
Open a spreadsheet in excel.
press f2 on any cell in the worksheet.

Expected behavior:

The nvda should read the characters entered in the cell when in edit mode.

Actual behavior:

after typing a content in the cell and pressing f2 to edit the cell, and trying to walk with the arrows by the typed text the nvda informs unknown, and does not read the typed text.

System configuration:

NVDA version:
next 14998

NVDA Installed or portable:
instaled

Other information:

Example: Running in a VM
it was necessary to reinstall the office so that nvda will read the texts typed in the cells again.
I tried to reinstall the nvda but it did not work.
I tried installing a previous version of nvda 2018.1 more unsolvable.
I tried to repair the oficce more also not solve.
The problem only resolved after you completely removed the office and re-installed the office.
Windows version:
windows 10 16299.309

Name and version of other software in use when reproducing the issue:
office 2016

Other questions:

Does the issue still occur after restarting your PC?
yes
Have you tried any other versions of NVDA?

Please list them and the result
2018.1

@fernando-jose-silva

This comment has been minimized.

Copy link
Author

fernando-jose-silva commented Apr 6, 2018

I also tried using the
Run COM Registration Fixing tool ...
in the nvda tools menu but it did not work.
Again, problem solved after uninstalling and reinstalling office 2016.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Apr 6, 2018

I can reproduce this with Next 14987, master and 2018.1 when running from source. I could be an issue in a specific Office build?

@fernando-jose-silva: Is this Office 365?

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Apr 6, 2018

I'm currently at Office build 2016.0.91.26

cc @dkager @bramd

@bramd

This comment has been minimized.

Copy link
Contributor

bramd commented Apr 6, 2018

Used Excel this afternoon and didn't see this issue, had some strange lag though that I should investigate. The laptop I used is still at the office, so can't check exact builds right now.

@dkager

This comment has been minimized.

Copy link
Collaborator

dkager commented Apr 6, 2018

I can reproduce with master and Office 2016 16.0.9126.2116.

@michaelDCurran

This comment has been minimized.

Copy link
Contributor

michaelDCurran commented Apr 6, 2018

@bramd

This comment has been minimized.

Copy link
Contributor

bramd commented Apr 6, 2018

@dkager

This comment has been minimized.

Copy link
Collaborator

dkager commented Apr 6, 2018

I did update regular Skype last week, which would be a terrible coincidence. :)

@fernando-jose-silva

This comment has been minimized.

Copy link
Author

fernando-jose-silva commented Apr 6, 2018

I'm using office 2016 it's not the 360 version.

@michaelDCurran

This comment has been minimized.

Copy link
Contributor

michaelDCurran commented Apr 6, 2018

@Brian1Gaff

This comment has been minimized.

Copy link

Brian1Gaff commented Apr 7, 2018

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Apr 9, 2018

I'm at Excel 16.0.9126.2109 at my work laptop. Here, the issue does not occur with latest next.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Apr 10, 2018

At the home laptop, I reinstalled Office and I'm now also at Excel 16.0.9126.2109. The issue still persists though. Skype for business is also a part of this new Office installation.

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Apr 12, 2018

The problem occurs on my desktop to which Windows did an update a couple of days ago. It does not happen on my notebook which has not yet received the update. Using 2018.1.1 on both machines. Looks like the office uninstall/reinstall is the fix for now - tedious.

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Apr 12, 2018

I neglected to mention that I am using Office 365. The updates that were applied to the desktop have just been applied to the notebook:
2018-04 Cumulative Update for Windows 10
Version 1709 for x64-based Systems (KB4093112)

2018-04 Security Update for Adobe Flash Player for
Windows 10 Version 1709 for x64-based Systems
KB4093110)

I can still edit Excel files on that machine. That puts my update theory into severe doubt.

@Qchristensen

This comment has been minimized.

Copy link

Qchristensen commented Apr 19, 2018

I'm sure when I first heard about this issue, editing was working fine for me. I just had another look and now I'm getting the "Unknown" issue as well. I am using an installed copy of NVDA Next so that has updated a couple of times. I ran a temporary copy of 2018.1.1 and the issue is occurring for me with that as well.

I'm using Windows 10 fast insider build 17134.1 and Office 365 which should be up to date. The account screen tells me Version 1803 Build 9126.2152 Click to run, Monthly channel.

I'm using the OneCore synth today, but swapping to eSpeak NG doesn't seem to change anything.

Looking at my NVDA log from where I pressed F2, then left arrow a couple of times:

IO - inputCore.InputManager.executeGesture (09:53:54.053):
Input: kb(desktop):f2
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:53:54.079):
oleacc.AccessibleObjectFromEvent with window 133528, objectID 30542 and childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:53:54.081):
oleacc.AccessibleObjectFromEvent with window 133528, objectID 30546 and childID 0: [Error -2147467259] Unspecified error
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (09:53:54.084):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (09:53:54.088):
Queue empty, done processing
DEBUGWARNING - NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor.get_isAlive (09:53:54.148):
could not compare sheet names
Traceback (most recent call last):
File "NVDAObjects\window\excel.pyo", line 452, in get_isAlive
File "comtypesMonkeyPatches.pyo", line 35, in new__getattr

File "comtypes\client\lazybind.pyo", line 168, in getattr
File "comtypes\automation.pyo", line 729, in _invoke
COMError: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUG - treeInterceptorHandler.killTreeInterceptor (09:53:54.148):
Killed treeInterceptor: <NVDAObjects.window.excel.ExcelBrowseModeTreeInterceptor object at 0x04FF0D50>
IO - speech.speak (09:53:54.153):
Speaking [LangChangeCommand (u'en_CA'), u'unknown']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (09:53:54.164):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (09:53:54.173):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (09:53:54.174):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (09:53:55.092):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (09:53:55.278):
Input: kb(desktop):leftArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (09:53:55.288):
Cancelling
IO - inputCore.InputManager.executeGesture (09:53:55.780):
Input: kb(desktop):leftArrow
IO - inputCore.InputManager.executeGesture (09:53:56.206):
Input: kb(desktop):leftArrow

@Qchristensen

This comment has been minimized.

Copy link

Qchristensen commented Apr 23, 2018

One quick update on this,

a suggestion from Pranav on the Users list was to uncheck "Allow editing in cells" on the "Advanced" page of Excel's options. This was checked by default, and I hadn't previously touched it, but unchecking it appears to have fixed the issue for me for now. I haven't tested extensively (I haven't restarted etc), but just at the moment it is working again.

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Apr 23, 2018

Unchecking Allow editing directly in cells also works around the issue here. I have restarted the machine. There was an initial glitch when trying to open an Excel file on restarting, but all seems good. NVDA now reports "Formula bar editing when pressing F2.

The Allow editing directly in cells is still checked on my notebook and the problem has not occurred there.

@ehollig

This comment has been minimized.

Copy link
Collaborator

ehollig commented Apr 25, 2018

Is this resolved, or is there still an issue here?

@Qchristensen

This comment has been minimized.

Copy link

Qchristensen commented Apr 26, 2018

It seems that unchecking the option to allow editing in cells seems to be a workaround for the issue, although it's more a band-aid than actually fixing it. Whether it's worth saying that is enough, I guess depends on what the underlying issue is, and possibly also whether the issue would still be relevant as and when we move to using UIA for Excel.

@k-kolev1985

This comment has been minimized.

Copy link

k-kolev1985 commented Apr 26, 2018

Yes, I can still reproduce the issue with the latest "next" snapshot of NVDA and the latest stable Excel 2016 (Office 365 version). Not only that, but almost each time when I close a file in Excel with Control+F4, Excel crashes. It does not crash with NVDA not running. But it also does crash with Narrator running, so the problem is somewhere in Excel/Office and not NVDA itself. Narrator at least reads the cell content when editing, even if the editing is done directly in the cell itself.

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Apr 26, 2018

I can confirm everything you mentioned except that Excel does not crash on exit with a screen reader running. I just tried reinstalling Office, which did not change anything. Not surprising, as it is not a clean install. No problems editing cells on my notebook machine, which seems to have all the updates of the desktop. I agree that it is not an NVDA issue per se - Microsoft has changed something.

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Apr 29, 2018

A further discovery which may or may not shed more light. I logged into my wife's account on the same machine and the problem does not occur there. Weird!

@clementb49

This comment has been minimized.

Copy link

clementb49 commented May 8, 2018

Hello,
I just would like to use excel for a task. I am facing this issue. I am using the last master of nvda (master-15110). I have just reinstall office 365. After I have run the com registration tool and I have reboot my laptop. The issue still occur. ²

@Qchristensen

This comment has been minimized.

Copy link

Qchristensen commented May 9, 2018

@clementb49 See this comment: #8146 (comment) if you turn off allow editing in cells it should fix the problem. Also see https://www.nvaccess.org/post/in-process-26th-april-2018/ for more information on the effects of that workaround.

I don't think the crashing is related. Could someone experiencing it (I'm not able to replicate it here either) could please create a new issue and include a copy of the NVDA log.

@k-kolev1985

This comment has been minimized.

Copy link

k-kolev1985 commented May 9, 2018

I was the one with the crashing bug of Excel with a screen reader running. But now I can't reproduce it anymore. When and if I do reproduce it, I'll provide NVDA's log and a memory dump from Excel, if necessary.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jul 17, 2018

I've seen this issue with Excel 2013. More importantly, the workaround to disable inline cell editing does not work, as it seems the formula bar isn't accessible. In my opinion this raises the importance of this issue a bit.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jul 17, 2018

@michaelDCurran: Would you agree with a p2 here?

@michaelDCurran

This comment has been minimized.

Copy link
Contributor

michaelDCurran commented Jul 17, 2018

@leonardder leonardder added the p2 label Jul 17, 2018

@andrew-l-d

This comment has been minimized.

Copy link

andrew-l-d commented Jul 17, 2018

The point that is worth reiterating here is that it is not something that broke in NVDA which caused the issue. I do not have the problem on one machine and on the other it only occurs in one account. Both machines have been through the same upgrade path. If an NVDA work-around can be found, well and good. However, it would be preferable to find out what happens in the system to create the problem.

Andrew

@zstanecic

This comment has been minimized.

Copy link
Contributor

zstanecic commented Jan 9, 2019

note that the issue #9137 is an example of the clean fresh office 365/windows installation.
This issue i have reported aksi frin ibe yser from the polish community

@kieranlittle667

This comment has been minimized.

Copy link

kieranlittle667 commented Feb 15, 2019

I'm still having this issue. I'm stil running 2018.3.2 however. My excel version is Microsoft® Excel® for Office 365 MSO (16.0.10730.20264) 32-bit.
This is a fresh installation of office 365 ProPlus on a fresh windows 10 1803 image.
I was also seeing the issue on my older work machine running the same software, but with windows 7 instead of 10.
I've just tried with JFW 2018 and that works fine. There's a little lag, but that's normal with excel these days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.