Jaws 16 closing chrome browser

[Jon M]

When running Jaws I am noticing that it will close the chrome browser and I am unable to re-open until I close Jaws?  Has anyone else been noticing this issue.

We will be switching our enterprise license to get Jaws 2018, I'll have more info if the same behavior occurs with that version of Jaws

[Dominic Mazzoni]

I haven't seen reports of that issue. Does Chrome ever actually crash? If you open the special web page chrome://crashes you might see some crash IDs - send those to us and we can investigate if so.

On Tue, Feb 20, 2018 at 3:05 PM Jon M <jd1983...@gmail.com> wrote:

When running Jaws I am noticing that it will close the chrome browser and I am unable to re-open until I close Jaws?  Has anyone else been noticing this issue.

We will be switching our enterprise license to get Jaws 2018, I'll have more info if the same behavior occurs with that version of Jaws

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessib...@chromium.org.

[Laura Eberly]

Hi Jon,

Adding on to what Dominic said, please let us know which version of Chrome you're running as well. The very latest Chrome Canary builds have had some freezing and strange interactions with JAWS in the last few days but if you're running the Stable, Beta, or Dev versions of Chrome we haven't seen that behavior. To clarify, Chrome Canary is meant to be bleeding-edge updates for developers while the other channels are meant more for end users with Stable being recommended for typical use. 

An easy way to let us know which version of Chrome you're using is to copy the top line from Chrome://version or to simply open a bug at CRBug.com. 

Thanks for writing in, looking forward to hearing more from you!

Thanks,

Laura 

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessibility+unsub...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessibility+unsub...@chromium.org.

[Jon M]

Laura,

Thank you for getting back to me. I do end user testing for a state Government website to validate user experience, so I have to test with the stable version.  I'd love to test with Canary but would not replicate user experience for SAAS upgrades. 

I took a screen shot of the my chrome version that i am testing with.  Also I am noticing that with Chrome on android it is not working with talk-back and behaving in a manner in which jaws would with chrome version 56.   

Here is the site I test: www.massanf.taleo.net/careersection/ex/jobsearch.ftl 

Thanks,

Jonathan

On Thu, Mar 1, 2018 at 1:12 AM, Laura Eberly <leb...@google.com> wrote:

Hi Jon,

Adding on to what Dominic said, please let us know which version of Chrome you're running as well. The very latest Chrome Canary builds have had some freezing and strange interactions with JAWS in the last few days but if you're running the Stable, Beta, or Dev versions of Chrome we haven't seen that behavior. To clarify, Chrome Canary is meant to be bleeding-edge updates for developers while the other channels are meant more for end users with Stable being recommended for typical use. 

An easy way to let us know which version of Chrome you're using is to copy the top line from Chrome://version or to simply open a bug at CRBug.com. 

Thanks for writing in, looking forward to hearing more from you!

Thanks,

Laura 

On Wed, Feb 28, 2018 at 9:59 PM, 'Dominic Mazzoni' via Chromium Accessibility <chromium-accessibility@chromium.org> wrote:

I haven't seen reports of that issue. Does Chrome ever actually crash? If you open the special web page chrome://crashes you might see some crash IDs - send those to us and we can investigate if so.

On Tue, Feb 20, 2018 at 3:05 PM Jon M <jd1983...@gmail.com> wrote:

When running Jaws I am noticing that it will close the chrome browser and I am unable to re-open until I close Jaws?  Has anyone else been noticing this issue.

We will be switching our enterprise license to get Jaws 2018, I'll have more info if the same behavior occurs with that version of Jaws

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessibility+unsubscri...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessibility+unsubscri...@chromium.org.

--

- Jonathan Murphy

[Dominic Mazzoni]

Note that the version of Chrome you're on (62) is two versions behind; the current stable version is 64. Is that your enterprise policy perhaps?

Even if Canary doesn't replicate the user experience it would be helpful to know if the problem reproduces with other versions of Chrome, just to narrow down the issue.

Not sure about Android but that version (56) is even older - though it should be working fine with TalkBack. Can you give any more detail on how it behaves?

Do you have these issues on all sites or just that site in particular?

On Thu, Mar 1, 2018 at 5:15 AM Jon M <jd1983...@gmail.com> wrote:

Laura,

Thank you for getting back to me. I do end user testing for a state Government website to validate user experience, so I have to test with the stable version.  I'd love to test with Canary but would not replicate user experience for SAAS upgrades. 

I took a screen shot of the my chrome version that i am testing with.  Also I am noticing that with Chrome on android it is not working with talk-back and behaving in a manner in which jaws would with chrome version 56.   

Here is the site I test: www.massanf.taleo.net/careersection/ex/jobsearch.ftl 

Thanks,

Jonathan

On Thu, Mar 1, 2018 at 1:12 AM, Laura Eberly <leb...@google.com> wrote:

Hi Jon,

Adding on to what Dominic said, please let us know which version of Chrome you're running as well. The very latest Chrome Canary builds have had some freezing and strange interactions with JAWS in the last few days but if you're running the Stable, Beta, or Dev versions of Chrome we haven't seen that behavior. To clarify, Chrome Canary is meant to be bleeding-edge updates for developers while the other channels are meant more for end users with Stable being recommended for typical use. 

An easy way to let us know which version of Chrome you're using is to copy the top line from Chrome://version or to simply open a bug at CRBug.com. 

Thanks for writing in, looking forward to hearing more from you!

Thanks,

Laura 

On Wed, Feb 28, 2018 at 9:59 PM, 'Dominic Mazzoni' via Chromium Accessibility <chromium-ac...@chromium.org> wrote:

I haven't seen reports of that issue. Does Chrome ever actually crash? If you open the special web page chrome://crashes you might see some crash IDs - send those to us and we can investigate if so.

On Tue, Feb 20, 2018 at 3:05 PM Jon M <jd1983...@gmail.com> wrote:

When running Jaws I am noticing that it will close the chrome browser and I am unable to re-open until I close Jaws?  Has anyone else been noticing this issue.

We will be switching our enterprise license to get Jaws 2018, I'll have more info if the same behavior occurs with that version of Jaws

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessib...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessib...@chromium.org.