Topics

problem with the newest chrome


P. Otter
 

i've the newest version of chrome.

the strange is, i've allso an old portable version ant the links will be displayed as usual.

there, in the old version the links are read by nvda.

in the newest version not at all!

so i think it is a problem of chrome, but other people in this list told that they had no problem at all in the newest version of chrome.

rather strange!

cheers

paul otter



Op 19-8-2016 om 16:10 schreef Kevin Chao:

1. What version of Chrome? 2. Please use "report an issue...'" in help menu.

On Fri, Aug 19, 2016 at 6:06 AM Gene <gsasner@...> wrote:
Then these problems may be Chrome problems.  I won't comment further and I'll wait to see what others may say. 
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 7:41 AM
Subject: Re: [nvda] problem with the newest chrome

The log is the NVDA log. In the nvda-translations list is a message about chrome, http://www.freelists.org/post/nvda-translations/Google-Chrome-support-is-broken-20163-should-alert-users-on-changest2t.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 13:11 schreef Gene:
Then this is evidently not an accessibility issue and I suspect it isn't a general problem with Chrome.  A sighted person probably wouldn't see links either and an error message is generated by Chrome, something that would not happen if this were an accessibility issue.  Try uninstalling and reinstalling Chrome.  You may have gotten a bad update. 
 
Also, since only one other person has reported an unclear problem with Chrome and certain links, that further supports the possibility that this is not a general Chrome problem.
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 6:50 AM
Subject: Re: [nvda] problem with the newest chrome

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>







Brian's Mail list account BY <bglists@...>
 

well from that error it looks as if nvda is setting the length of the text to less than 1, by setting its end point before its start and assumedly this will mean no text will be seen there. How very peculiar..

I don't use Chrome but can say that in Firefox 48 the bugs I mentioned in that program seem to have been resolved again. The pre releases had some issues about the navigational sounds add on and some other minor irritations.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Friday, August 19, 2016 12:55 PM
Subject: Re: [nvda] problem with the newest chrome


   hello, it is the first option you mention.

when i do a google search i don't see the links.

and the most strange in this situation is, i see the rule that you find under the link, i can read it.

when i go with the arrow up, therw where i supose the link, i press enter, the link is working as usual!

so, the link is there, only not read by nvda.

i don't know what that is.

Â


cheers
paul otter


Op 19-8-2016 om 13:01 schreef Gene:

Chrome automatically updates itself and the user can't stop it. Use Firefox for sites where you have this problem. It isn't clear to me what the problem is. Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
Â
Gene
----- Original Message -----

From: Brian's Mail list account
Sent: Friday, August 19, 2016 3:31 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] problem with the newest chrome


One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell The Chrome team and nvda team about any issues and back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming
up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search
results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>







Gene
 

It should be pointed out that those reporting problems aren't stating the version of Windows being used.  Those who are reporting no problems are also not providing such information.  That might be at least one reason that people are reporting different results.
 
Gene

----- Original Message -----
From: Gene
Sent: Friday, August 19, 2016 8:07 AM
Subject: Re: [nvda] problem with the newest chrome

Then these problems may be Chrome problems.  I won't comment further and I'll wait to see what others may say. 
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 7:41 AM
Subject: Re: [nvda] problem with the newest chrome

The log is the NVDA log. In the nvda-translations list is a message about chrome, http://www.freelists.org/post/nvda-translations/Google-Chrome-support-is-broken-20163-should-alert-users-on-changest2t.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 13:11 schreef Gene:
Then this is evidently not an accessibility issue and I suspect it isn't a general problem with Chrome.  A sighted person probably wouldn't see links either and an error message is generated by Chrome, something that would not happen if this were an accessibility issue.  Try uninstalling and reinstalling Chrome.  You may have gotten a bad update. 
 
Also, since only one other person has reported an unclear problem with Chrome and certain links, that further supports the possibility that this is not a general Chrome problem.
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 6:50 AM
Subject: Re: [nvda] problem with the newest chrome

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>






 

I use Windows 10 build 14393 32-bit.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 16:22 schreef Gene:

It should be pointed out that those reporting problems aren't stating the version of Windows being used.  Those who are reporting no problems are also not providing such information.  That might be at least one reason that people are reporting different results.
 
Gene
----- Original Message -----
From: Gene
Sent: Friday, August 19, 2016 8:07 AM
Subject: Re: [nvda] problem with the newest chrome

Then these problems may be Chrome problems.  I won't comment further and I'll wait to see what others may say. 
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 7:41 AM
Subject: Re: [nvda] problem with the newest chrome

The log is the NVDA log. In the nvda-translations list is a message about chrome, http://www.freelists.org/post/nvda-translations/Google-Chrome-support-is-broken-20163-should-alert-users-on-changest2t.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 13:11 schreef Gene:
Then this is evidently not an accessibility issue and I suspect it isn't a general problem with Chrome.  A sighted person probably wouldn't see links either and an error message is generated by Chrome, something that would not happen if this were an accessibility issue.  Try uninstalling and reinstalling Chrome.  You may have gotten a bad update. 
 
Also, since only one other person has reported an unclear problem with Chrome and certain links, that further supports the possibility that this is not a general Chrome problem.
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 6:50 AM
Subject: Re: [nvda] problem with the newest chrome

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>







Kevin Chao
 

Chrome has 4 different channels (Canary, Dev, Beta, and Stable), and they update at different times. Specifying "latest version" isn't useful for debugging purposes, so 

please copy/paste the value that chrome://version provides 

Thanks!

On Fri, Aug 19, 2016 at 8:37 AM Artin Dekker <artindekker@...> wrote:

I use Windows 10 build 14393 32-bit.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 16:22 schreef Gene:
It should be pointed out that those reporting problems aren't stating the version of Windows being used.  Those who are reporting no problems are also not providing such information.  That might be at least one reason that people are reporting different results.
 
Gene
----- Original Message -----
From: Gene
Sent: Friday, August 19, 2016 8:07 AM
Subject: Re: [nvda] problem with the newest chrome

Then these problems may be Chrome problems.  I won't comment further and I'll wait to see what others may say. 
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 7:41 AM
Subject: Re: [nvda] problem with the newest chrome

The log is the NVDA log. In the nvda-translations list is a message about chrome, http://www.freelists.org/post/nvda-translations/Google-Chrome-support-is-broken-20163-should-alert-users-on-changest2t.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 13:11 schreef Gene:
Then this is evidently not an accessibility issue and I suspect it isn't a general problem with Chrome.  A sighted person probably wouldn't see links either and an error message is generated by Chrome, something that would not happen if this were an accessibility issue.  Try uninstalling and reinstalling Chrome.  You may have gotten a bad update. 
 
Also, since only one other person has reported an unclear problem with Chrome and certain links, that further supports the possibility that this is not a general Chrome problem.
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 6:50 AM
Subject: Re: [nvda] problem with the newest chrome

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>







 

Google Chrome:
52.0.2743.116 (Official build) m(32-bits)
Revision:
9115ecad1cae66fd5fe52bd9120af643384fd6f3-refs/branch-heads/2743@{#728}

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 16:44 schreef Kevin Chao:

Chrome has 4 different channels (Canary, Dev, Beta, and Stable), and they update at different times. Specifying "latest version" isn't useful for debugging purposes, so 

please copy/paste the value that chrome://version provides 

Thanks!

On Fri, Aug 19, 2016 at 8:37 AM Artin Dekker <artindekker@...> wrote:

I use Windows 10 build 14393 32-bit.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 16:22 schreef Gene:
It should be pointed out that those reporting problems aren't stating the version of Windows being used.  Those who are reporting no problems are also not providing such information.  That might be at least one reason that people are reporting different results.
 
Gene
----- Original Message -----
From: Gene
Sent: Friday, August 19, 2016 8:07 AM
Subject: Re: [nvda] problem with the newest chrome

Then these problems may be Chrome problems.  I won't comment further and I'll wait to see what others may say. 
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 7:41 AM
Subject: Re: [nvda] problem with the newest chrome

The log is the NVDA log. In the nvda-translations list is a message about chrome, http://www.freelists.org/post/nvda-translations/Google-Chrome-support-is-broken-20163-should-alert-users-on-changest2t.

Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 13:11 schreef Gene:
Then this is evidently not an accessibility issue and I suspect it isn't a general problem with Chrome.  A sighted person probably wouldn't see links either and an error message is generated by Chrome, something that would not happen if this were an accessibility issue.  Try uninstalling and reinstalling Chrome.  You may have gotten a bad update. 
 
Also, since only one other person has reported an unclear problem with Chrome and certain links, that further supports the possibility that this is not a general Chrome problem.
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 6:50 AM
Subject: Re: [nvda] problem with the newest chrome

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>








Dejan Ristic
 

Now that you've said what the problem is, try using Firefox for the time being, for I do it when Chrome is not as reliable as before.


On 8/19/2016 1:50 PM, Artin Dekker wrote:

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>








Dejan Ristic
 

What do you say as to the Opera browser? Is it possible for you to use that one instead? Is its behaviour similar to that of Chrome?


On 8/19/2016 1:55 PM, P. Otter wrote:

    hello, it is the first option you mention.

when i do a google search i don't see the links.

and the most strange in this situation is, i see the rule that you find under the link, i can read it.

when i go with the arrow up, therw where i supose the link, i press enter, the link is working as usual!

so, the link is there, only not read by nvda.

i don't know what that is.

 

cheers
paul otter

Op 19-8-2016 om 13:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>




.




Dejan Ristic
 

It is possible for me to hear the links in Chrome, but it is impossible to read the lists of the source and target languages in Google Translate via Chrome, though. That's what I have faced when Google chrome has updated itself. I have also tried Opera, but the same goes for it. Then, I have tried Avast! Safe Zone Browser, and it has also failed. Let me conclude that these ones are the Chrome-based engines, and that they sing the same song at the same time.


On 8/19/2016 2:07 PM, P. Otter wrote:

it is right what you write!

no link will be displayed in chrome only in the own settings of chrome!

paul otter




Op 19-8-2016 om 13:50 schreef Artin Dekker:

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>





.




Dejan Ristic
 

Allow me to say that I use Windows 7, Ultimate, 64Bit SP1, and the latest version of all the browsers and NVDA.


On 8/19/2016 7:01 PM, Dejan Ristic wrote:

It is possible for me to hear the links in Chrome, but it is impossible to read the lists of the source and target languages in Google Translate via Chrome, though. That's what I have faced when Google chrome has updated itself. I have also tried Opera, but the same goes for it. Then, I have tried Avast! Safe Zone Browser, and it has also failed. Let me conclude that these ones are the Chrome-based engines, and that they sing the same song at the same time.


On 8/19/2016 2:07 PM, P. Otter wrote:

it is right what you write!

no link will be displayed in chrome only in the own settings of chrome!

paul otter




Op 19-8-2016 om 13:50 schreef Artin Dekker:

If I have a link in Chrome NVDA says blank. This happens at every link, not only in search results. The log is:

ERROR - XMLFormatting.XMLTextParser.parse (12:46:30):
XML: <control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5026" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="22" _childcontrolcount="22" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_tag="#document" IAccessible2::state_1024="1" IAccessible::role="15" IAccessible::state_1048576="1" IAccessible::state_64="1" keyboardShortcut="" name="Microsoft – Official Home Page" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5027" _startOfNode="1" _endOfNode="0" isBlock="1" isHidden="0" _childcount="5" _childcontrolcount="4" _indexInParent="0" _parentChildCount="22" IAccessible2::attribute_class="shell-header shell-responsive  global-sticky mobile-view" IAccessible2::attribute_display="block" IAccessible2::attribute_id="shell-header" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="banner" IAccessible2::state_1024="1" IAccessible::role="1043" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5031" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="0" _parentChildCount="5" IAccessible2::attribute_display="block" IAccessible2::attribute_id="srv_shellHeaderMicrosoftLogo" IAccessible2::attribute_tag="a" IAccessible2::state_1024="1" IAccessible::role="30" IAccessible::state_1048576="1" IAccessible::state_4194304="1" IAccessible::state_8388608="1" IAccessibleAction_Gaan naar="0" description="Microsoft" keyboardShortcut="" ><control controlIdentifier_docHandle="1836924" controlIdentifier_ID="-5035" _startOfNode="1" _endOfNode="1" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" IAccessible2::attribute_display="block" IAccessible2::attribute_explicit-name="true" IAccessible2::attribute_src="https://assets.onestore.ms/cdnfiles/onestorerolling-1608-09000/shell/v3/images/logo/microsoft.png" IAccessible2::attribute_tag="img" IAccessible2::attribute_xml-roles="img" IAccessible2::state_1024="1" IAccessible::role="40" IAccessible::state_4194304="1" IAccessible::state_64="1" IAccessibleAction_klikken="0" keyboardShortcut="" ><text _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="0" _childcontrolcount="0" _indexInParent="0" _parentChildCount="1" >Microsoft</text></control></control></control></control>
Traceback (most recent call last):
  File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 1516


Artin Dekker
Beheerder win10-nl
https://win10-nl.groups.io/g/algemeen
Op 19-8-2016 om 12:01 schreef Gene:
Chrome automatically updates itself and the user can't stop it.  Use Firefox for sites where you have this problem.  It isn't clear to me what the problem is.  Is the problem that when you do a search such as a google search, you don't see the links in the results displayed as clickable links or you don't see the address of the sites in the results showing where the result leads?
 
Gene
----- Original Message -----
Sent: Friday, August 19, 2016 3:31 AM
Subject: Re: [nvda] problem with the newest chrome

One of the things I soon learned was to keep archives of older versions of
software so one could back track if things got broken. For the moment all
you can do is tell  The Chrome team and nvda team about any issues and  back
track to the earlier viersion until its been fixed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "P. Otter" <pam.otter@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 18, 2016 6:24 PM
Subject: [nvda] problem with the newest chrome


> hello all,
>
> i've a problem with the newest version of chrome.
>
> when i type a search string for example nvda the results will coming up,
> but the link will not be spoken.
>
> what's wrong?
>
> i've allso an older version, but that's a portable version.
>
> when i open this version the results will be spoken allso the links.
>
> what can i do to solve this problem and are there more people who has
> problems like this in chrome?
>
> i was just glad that i could use chrome in nvda.
>
> the same problem comes up when i open youtube after i have search results.
>
> i don't understand why this is changed.
>
> before chrome was working perfectly!
>
> thanks in advance.
>
> paul otter
>
>
>
>
>





.







Zack Nichols
 

I'm a web developer working on supporting NVDA with Chrome at the moment, and I'm having a similar problem with the Kendo UI menu control found here: Kendo UI Menu Keyboard Navigation

It's not reading the menu items for me, while Firefox reads them (albeit with a bug or two). I posted this issue in the Chrome support forum: Google Product Forums


Zack Nichols
 

My particular problems appears to be resolved in Chrome version 53 (the current beta) which is projected to be released as stable the week of September 6th.