Issue metadata
Sign in to add a comment
|
Long PDFs don't appear in the PDF viewer when using Jaws |
||||||||||||||||||||||
Issue description1. Start Jaws 18. 2. Open Chrome 63, or any other recent version, since bug doesn't seem to be version related. 3. Navigate to a long PDF such as the following http://files.accuvant.com/web/files/AccuvantBrowserSecCompar_FINAL.pdf 4. Notice that the contents of the PDF don't appear in the virtual buffer. 5. Try refreshing the buffer with JawsKey+Esc and notice that the issue doesn't go away. 6. Start NVDA and notice that you can read the PDF fine. 7. Quit NVDA and navigate to a shorter PDF with Jaws. 8. Notice that Jaws reads the contents correctly.
,
Dec 9 2017
,
Dec 11 2017
,
Dec 12 2017
Is it possible it's just slow? We should test by logging when it completes and try some PDFs of different sizes. Also we should just make it load accessibility progressively. Right now it waits until the whole doc is loaded to expose accessibility.
,
Dec 12 2017
,
Dec 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by thestig@chromium.org
, Sep 25 2017