Issue metadata
Sign in to add a comment
|
Can't use arrow keys to scroll up/down until after page is clicked
Reported by
khym.cha...@gmail.com,
Jul 16 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Example URL: https://brytewave.com/ Steps to reproduce the problem: 1. Go to https://brytewave.com 2. Get an account 3. Get access to a textbook 4. Go to any page within the textbook. 5. Go to the next or previous page, either using the left or right arrow keys or by clicking the left or right arrow icons which appear on the page while hovering the 6. Attempt to scroll up or down the page using the up or down arrow keys. What is the expected behavior? You can scroll up and down using the arrow keys. What went wrong? You cannot scroll up or down using the arrow keys until you use the mouse to click somewhere inside the page. After that you'll be able to scroll up and down with the arrow keys until you go to the next or previous page. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? No Firefox 54.0 Chrome version: 59.0.3071.115 Channel: stable OS Version: Fedora 25 Flash Version: Shockwave Flash 26.0 r0 If you click inside the page (not on one of the arrow icons) you'll get this error in the console: Error: Node [object HTMLDivElement] not found. Partial CFI found: https://jigsaw.vitalsource.com/assets/v1/jigsaw/puzzle_pieces/index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js If, after clicking inside the page, you go to the next or previous page via using the arrow keys, you'll then get this error message in the console: Uncaught TypeError: Cannot read property 'words' of undefined at Object.contentReady (index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:6) at Object.callBookTypeContentReady (index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:7) at Object.initNextPage (index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:7) at Object.<anonymous> (index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:9) at i (index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:4) contentReady @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:6 callBookTypeContentReady @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:7 initNextPage @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:7 (anonymous) @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:9 i @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:4 13:09:33.842 index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:3 XHR finished loading: POST "https://jigsaw.vitalsource.com/api/v0/books/9781457649905/logs". send @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:3 ajax @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:3 a.flush @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:9 (anonymous) @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:9 fire @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:4 (anonymous) @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:6 (anonymous) @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:9 i @ index-6db1d21de39e903ec0a6fd1befbffd80eed844ecda9f03b7d94a3e49aac30acd.js:4
,
Jul 17 2017
Tested this issue on Ubuntu 14.04 using chrome latest stable #59.0.3071.115 by following steps mentioned below. 1. Navigated to https://brytewave.com 2. Created a new account 3. Observed to get access in to text book required credit card details Reporter@ Could you please provide any test account if available where we can access the text book or please provide a sample test case to check this issue from Chrome-TE end. Thanks!
,
Jul 18 2017
Sorry, I'm not with BryteWave.com, so I can't give a test account, nor do I have access to the code such that I could strip it down to a test case.
,
Jul 18 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2017
Since there is no test case available to check this issue from Chrome-TE end, Requesting someone from blink team to look in to it. Thanks!
,
Jul 21 2017
I've reached out to their customersupport to see if we can connect with their engineering team.
,
Jul 27 2017
,
Aug 3 2017
The NextAction date has arrived: 2017-08-03
,
Aug 3 2017
We haven't received a response from the website and it's been about 2 weeks. Unfortunately there isn't much we can do here. This is likely to be an issue with the page itself rather than Chrome so I'm going to mark this as WontFix. If we get a response and a link we can debug we can reopen. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jul 17 2017