Hi,

This is affecting a number of customers, can this please be looked at, as it is only occurring in Chrome - not other browsers. 

Took the bug, and following up w/ the customer for some test credentials.
In the meantime, would be really great to have some help from Chrome QA on this one.

Many thanks,

I'm able to navigate on the site, scroll and click
username & password:
https://drive.google.com/open?id=1KUASNmZE6jHGb7j4ZAyKSFrzzuultbi7dmYgS8k53-o
Versions of ChromeOs tested:
https://drive.google.com/open?id=1hyhxMEaeEHV2JhPfImgLErY0ugcJmKVP74Gxj9CvccU

We could not repro this issue, could QA give it a try, please?

hi George, we're a bit stuck in this investigation on the Support side - could you please help us out?
Many thanks

Hi All, 

THis is an interesting issue, it works on some chrome OS platforms but not others. I have not been able to narrow it down. For examply works fine on my ASUS N62 chromebox and pixel 1 but not acer c720. But then sometimes it works for some users but not others across a few different OS versions. I exhausted my investigations, hence the call being logged and issue raised on chromium. I can assist if needed. 

Thank you srcrew@ - I've reached out to the team as well. I'd expect some news after the US holidays time. Steve or somebody from the TSE team will reach out to you via the case within this week.

more details from customer at: https://drive.google.com/a/google.com/file/d/0BwQr3Yf1hJdyaUtzdVNqaE5OVEE/view?usp=sharing

@Scott (srcrew@): could you please make the Chrome > Developer tools > Console and capture the output shown there? I'm interested in any errors or device/OS capabilities required for the site to show-up, look for exceptions in the console.

Many thanks,

Google Chrome	59.0.3071.91 (Official Build) (32-bit)
Revision	0
Platform	9460.60.0 (Official Build) stable-channel veyron_minnie
Firmware Version	Google_Veyron_Minnie.6588.237.0
ARC	4059099
JavaScript	V8 5.9.211.31
Flash	26.0.0.102 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS armv7l 9460.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.91 Safari/537.36
Command Line	/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=26.0.0.102 --ui-prioritize-in-gpu-process --use-gl=egl --gpu-sandbox-failures-fatal=yes --gpu-sandbox-start-early --enable-logging --log-level=1 --use-cras --enable-wayland-server --arc-availability=officially-supported --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --enable-hardware-overlays=single-fullscreen --login-profile=user --has-chromeos-keyboard --enable-touchview --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-prefixed-encrypted-media --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --first-exec-after-boot --vmodule=*arc/*=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2
Executable Path


on the console we have
HomePage.do:1654 [Violation] 'load' handler took 556ms
[Violation] Forced reflow while executing JavaScript took 43ms
framework.js?appVersion=1.1:1 [Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive.
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 652ms
[Violation] Forced reflow while executing JavaScript took 47ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 204ms
[Violation] Forced reflow while executing JavaScript took 50ms
[Violation] Forced reflow while executing JavaScript took 42ms
framework.js?appVersion=1.1:1 [Violation] 'requestAnimationFrame' handler took 452ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 178ms
framework.js?appVersion=1.1:1 [Violation] 'contextmenu' handler took 217ms
[Violation] Forced reflow while executing JavaScript took 40ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 163ms



HomePage.do:1654 [Violation] 'load' handler took 556ms
[Violation] Forced reflow while executing JavaScript took 43ms
framework.js?appVersion=1.1:1 [Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive.
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 652ms
[Violation] Forced reflow while executing JavaScript took 47ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 204ms
[Violation] Forced reflow while executing JavaScript took 50ms
[Violation] Forced reflow while executing JavaScript took 42ms
framework.js?appVersion=1.1:1 [Violation] 'requestAnimationFrame' handler took 452ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 178ms
framework.js?appVersion=1.1:1 [Violation] 'contextmenu' handler took 217ms
[Violation] Forced reflow while executing JavaScript took 40ms
framework.js?appVersion=1.1:1 [Violation] 'readystatechange' handler took 163ms

We had a look at the console with a local google rep, we could find no errors. 

@  ashokkum, can you please assist. 

Tested on Chrome Stable #59.0.3071.115 and Canary #61.0.3147.0 on Windows 10, Mac 10.12.5 & Ubuntu14.04 and issue is not reproducible. Please refer the screencast attached
 
@ashokkumar -- Could you please try updating your Chrome to latest stable version as mentioned and by removing the extensions and creating a new profile to verify if the issue still persists.
 
Please let us know if we have missed anything.
 
Thanks in advance.

Deleted: 716312.mov 7.9 MB

716312.mov 7.9 MB Download

hi Praphulla & many thanks for looking into this.

I tried this myself on an Acer (with marcore@): the issue does reproduce. You need to further click on the left-pane three and you will notice the UI soon starts acting up.

Please follow-up the details provided by the customer and linked in Comment#13. Soon after a few clicks around, on the Acer device:
- the right-click on the three of options stops working (right-click doesn't show the contextual menu)
- also the drag&drop is not working: create a test (as Scott indicated in the reproduction steps documented in Comment #13) and try to link it - doesn't work either
Please reach out to me or marcore@ and let's do this together - happy to help as much as we can

Latest repro update from our QA team: https://drive.google.com/open?id=0B91MtOa4hcAbS2dUTmUxd3hidGc

Bumping to P1: This is major impairment for the domain, usage of these tools is blocked on Chrome.

Updated link for the supporting data mentioned in Comment #18:

https://drive.google.com/drive/folders/0B6f2eouJNPc_OEhGQlVhYk55a1U?usp=sharing

Created new link as access was requested by Scott.

Adding RBS to raise visibility and reassigning to TPM. 
We need some response from Eng to set expectations with customer.

It's too late for M60, but may be possible to get in for M61.

This needs a reliable repro and an eng owner, I don't have access to the Drive link in #20.  Can you just add a summary of the details to the bug here?  Like repro steps, urls, devices this fails on.

+blumberg@ and abdulsyed@

If this has been around since M57, we should not mark this is RB-Stable.

Please provide access to Google Docs in #20, or please post details here in the bug. This seems to be impacting a specific internal tool; can you please provide exact steps for how this can be recreated and if there are test credentials?

So far: 
OS: Windows 7
Device: Acer

Please update the bug title

URGENT - PTAL.
Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the M61 branch #3163 ASAP to have enough baking time in Beta before Stable promotion. Thank you!

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label.

removing urgency until we get more data from bug creator.

Closing, as there are issues with customer's code. Will re-open if find specific misbehavior with chrome's javascript or html