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

Regression for Windows Date and Time Information Dialogue #1637

nvaccessAuto opened this issue Jul 2, 2011 · 1 comment

Regression for Windows Date and Time Information Dialogue #1637

nvaccessAuto opened this issue Jul 2, 2011 · 1 comment


Copy link

Reported by m11chen on 2011-07-02 04:07
When the Date and Time Information Dialogue is opened by pressing Enter on the clock in the system tray, NVDA can no longer read the calendar.

Steps to reproduce:

  1. Press Windows+B to go to the system tray.
  2. Press LeftArrow to go to the clock.
  3. Press enter to open the "Date and Time Information" dialogue.

Expected result:
NVDA should read the day of week, month and date under the system focus. In 2011.1, this could also be done after using the arrow keys to move around the calendar followed by pressing NVDA+UpArrow.

Current result:
NVDA says "Calendar control" regardless of the system focus. Pressing NVDA+UpArrow also speaks "Calendar control" and nothing else.

I am running English version 64-bit Windows 7, but I have also tested on Traditional Chinese XP and the problem seems to be specific to Win7. However, in XP, NVDA 2011.1 used to only announce the date and month but not the day of week, and this is still the case for 2011.2beta1.

Copy link

Comment 1 by mdcurran on 2011-07-04 04:22
Fixed in 21a0d33. However, this changeset goes above and beyond this ticket. Now support for this control is the same as in Windows Vista (i.e. NVDA announces the new date when its changed with the arrow keys). The bug that this ticket talks about happened when we changed the way we detect and filter out proxied UI Automation elements. The element with focus was being ignored as it had no native windowHandle, and it apparently was an MSAA proxy (according to providerDescription). However it was broken in other ways such as the runtimeID, frameworkID, className all being empty, which is strange for an MSAA proxy. So now for SysMonthCal32 we simply refuse to use UI Automation at all as we cannot trust it.
Thanks for reporting! :)
Milestone changed from None to 2011.2
State: closed

@nvaccessAuto nvaccessAuto added this to the 2011.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant