Issue metadata
Sign in to add a comment
|
Links do not work after window resize
Reported by
jongran...@gmail.com,
Aug 16 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Example URL: http://www.bbc.co.uk/news or any website Steps to reproduce the problem: 1. Visit any website 2. Resize the window, on teh right side, or on the corner (using the mouse) 3. Observe, hover the mouse over links, observe than none work. What is the expected behavior? Links should turn blue when mouse over them, and URL visible in bottom of browser What went wrong? Links did not turn blue, URL not visible at bottom of browser Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 60.0.3112.90 Channel: n/a OS Version: Latest Ubuntu LTS Flash Version:
,
Aug 16 2017
I can reproduce it every time, by following those steps Is your browser full screen? That would prevent it from happening. Browser must be in a window. Could you try in Ubuntu LTS please. Thank you. I reset the flags on chrome://flags Still reproducible Opened Incovnito Still reproducible Tried in Firefox, all web site links still working after a window resize event.
,
Aug 16 2017
No, I'm not full screen. And I'm trying this from Ubuntu 14.04 LTS. Do mouse clicks still work? Can you select text? Scroll around, etc? Does reloading or navigating to a new page fix the issue? Unless we can reproduce this it'll be difficult to make any progress. I suspect this might be something in your environment (many Chrome devs use Linux and this seems like a common repro so I'd expect this would be hit regularly) but we'll leave the bug open and see if we get other reports.
,
Aug 16 2017
14.04 isn't latest LTS. Could you try latest LTS 16.04 please With Gnome desktop. Perhaps in a VM. Or someone else can try. yes, moving the scroll slider on the window fixes it. I imagine it hasn't retained focus for some reason. Firefox doesn't have the problem, and none of the other applications. -- Alternatively, if you are familiar with the code for this window focus, could take a look...
,
Aug 16 2017
Unfortunately I don't have 16.04, but if it's an issue caused by the version it's likely a bug in Ubuntu or one of the associated packages and not Chrome. Chrome should be performing hover actions even if it's not focused. Without being able to reproduce the issue it'd be impossible for me to track it down and debug it. However, if someone else can repro it and does have the skills I'd be happy to provide guidance and code reviews to get a fix merged.
,
Aug 19 2017
I'm using "GNOME Flashback (Compiz)" desktop. Could you try that perhaps. I imgagine it could be window focus issue. Firefox is working ok though
,
Aug 24 2017
Tested the issue on ubuntu 14.04 LTS and 16.04 LTS with GNOME Flashback (compiz) window manager on chrome stable M60 #60.0.3112.101 and issue is not reproduced. Attached screencast for reference. @jongrantuk-- Please check attached screencast and let us know if we had missed any steps in reproducing the issue. Thanks!
,
Aug 24 2017
Bit of a long shot but ,jongrantuk@, could you start a trace (see https://www.chromium.org/developers/how-tos/submitting-a-performance-bug), perform the resize and try scrolling, then attach the the trace here. If the wheel events are getting to Chrome we might be able to see where they end up getting dropped. (if they don't make it to Chrome though we might be out of luck).
,
Aug 24 2017
Trace added
,
Aug 24 2017
Thank you for providing more feedback. Adding requester "hdodda@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
,
Aug 24 2017
Example
,
Aug 25 2017
Thanks for the trace. It looks like the after the resize (around the 6.8 second mark), the browser doesn't see any input events, not even mouse moves :/ I suspect we might not be correctly resetting some state with the window manager. Unfortunately, I'm at the limits of my knowledge and without a repro I can't debug. +sadrul@ in case you have some ideas on how we might be able to get more information/debugging.
,
Aug 28 2017
Looking at the trace there are DesktopWindowTreeHostX11::Dispatch but no targetting to a RenderWidgetHostViewBase Could this be a views targeting issue?
,
Aug 30 2017
The NextAction date has arrived: 2017-08-30
,
Sep 5 2017
Unable to reproduce the issue on Ubuntu 14.04 using latest stable#60.0.3112.113 as per C#0 & C#11. Links turned to blue when mouse over and URL visible in bottom of browser. Please find the attached screencast for reference & let us know your observations on the same. Thanks..!!
,
Sep 5 2017
Ubuntu 14.04 is out of date. Worth trying with latest Ubuntu LTS 16.04 Reproduced every time in 16.04
,
Sep 5 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@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
,
Sep 6 2017
Unable to reproduce the issue on Ubuntu 16.04 using chrome reported version-60.0.3112.90 & stable-61.0.3163.79 as per steps mentioned in comment#0. Links turned to blue when mouse over and URL visible in bottom of browser. Please find the attached screencast for reference & let us know your observations on the same. Thanks..!!
,
Sep 6 2017
Hi. Thank you for the video from 16.04, but it looks like you are not using the same window manager to reproduce. Should be GNOME Flashback (compiz) window manager Thank you Jonny
,
Sep 6 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@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
,
Sep 6 2017
jongrantuk@: If it happens only on a specific window manager, and not on others, then it's probably related to that window-manager. A long while back (~2010/2011), when we started switching to xinput2 for input events, there used to be an issue in one of the gnome window managers (whichever was the default on ubuntu, I think) where the chrome app would never receive a mouse-up/mouse-release event. Something like that could explain the behaviour described in comments #12 and #13 (if chrome never receives the mouse-release, then the implicit capture in views will never be reset, which means the position-based targeting will not happen for subsequent mouse-moves). Does clicking on the window 'fix' the issue?
,
Sep 6 2017
Yes, I think I said, clicking on the window fixes it. I uploaded a video showing that workaround. Firefox and all other apps can be resized ok. Can one of the software engineers investigate and fix?
,
Sep 6 2017
Thank you for providing more feedback. Adding requester "sadrul@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
,
Sep 7 2017
Thanks for the update! Unfortunately not able to reproduce the issue from TE end.Some one from Internals>Views>Desktop dev team please look in to this issue. Thank You!
,
Nov 6 2017
Could some one from cc'ed dev / Internals>Views>Desktop team , please take a look into this issue. Thanks in advance..!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Aug 16 2017