Issue metadata
Sign in to add a comment
|
Randomly toggles fullscreen forth and back when dragging Developer Tools tab separator while emulating mobile
Reported by
teo8...@gmail.com,
Jul 9
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Open the Developer Tools and turn on Mobile emulation 2. open any website 3. drag the horizontal separator bar between the Developer Tools and the tab, in order to enlarge the Developer Tools. Move it upwards and then downwards What is the expected behavior? should just drag the separator and enlarge one tab and shrink the other, nothing else should happen. There's no reason to go to fullscreen automatically. And even if that was a good idea, it should happen smoothly and at a predictable threshold (with some hysteresis), without any crazy back-and-forth dozen-times-per-second switching. What went wrong? When you reach a certain point moving the bar up, suddenly the whole window goes crazy and starts going fullscreen and back to normal, like several times per second, then sometimes it randomly stabilizes on fullscreen. Then the behavior is utterly random. Sometimes even if you drag it back down to the original position, it will remain in fullscreen, sometimes it will switch back to normal. Usually, by moving the bar nervously up and down quicly, you will manage to have it switch back to normal mode and remain like that, even at a higher position. It's a complete fucking mess. Did this work before? Yes not sure, but I'm pretty sure it used to Chrome version: 67.0.3396.99 Channel: stable OS Version: Flash Version:
,
Jul 9
Fascinating. Thank you very much for reporting. Can you capture a video of this? We've tried but so far we're unable to reproduce this.
,
Jul 9
> Can you capture a video of this? We've tried but so far we're > unable to reproduce this. Unfortunately I can't reproduce it anymore either (I'm not sure whether I have restarted Chrome since it happened, I have certainly suspended and resumed the computer). Can you suggest a tool for recording video screen captures in Ubuntu that works smoothly out of the box?
,
Jul 9
some folks on our team use kazam https://launchpad.net/kazam
,
Jul 9
I see, it's a specific URL that reproduces the issue: (WARNING: it's a porn site again) https://www.youporn.com/watch/8136841/cute-chubby-chicks-fucking-in-a-threesome/ Maybe there's some javascript in the page that actually toggles fullscreen. However: - that seems a bit unlikely - shouldn't the browser ask for permission to enter fullscreen at least the first time? Isn't that what it does on a real mobile device the first time a given domain wants to go fullscreen from JavaScript (especially not initiated by true user interaction)? And even if it's really javascript entering fullscreen mode and legitimately so: - the emulator should emulate fullscreen within the emulated device screen. It makes absolutely no sense to enter fullscreen mode in the "host" browser on desktop. But I think I reported the last point in a separate bug quite a while ago.
,
Jul 9
> But I think I reported the last point in a separate bug quite a while ago. Here it is: https://bugs.chromium.org/p/chromium/issues/detail?id=628928 "Archived". The very concept of "archiving" a bug is beyond my understanding.
,
Jul 10
As per comment #0 tested this issue and Unable to reproduce the issue on reported chrome version 67.0.3396.99 using Ubuntu 17.10. Attaching screencast for reference. Steps: --------- 1. Launched reported chrome 1. Opened the Developer Tools and turned on Mobile emulation 2. Navigated to "https://www.youtube.com/?gl=IN","https://www.google.com/" 3. Dragged the horizontal separator bar between the Developer Tools and the tab. Moved it upwards and then downwards As we are observed that its not shifted to fullscreen mode. @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here. Thanks.!
,
Jul 10
> and confirm if anything being missed here Something is being missed here: comment 5.
,
Jul 10
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11
As per C#2 and C#3 this seems to be inconsistent. Hence removing the Needs-Bisect label and could someone from the dev tool team take a look at this and help in triaging this further. Thanks..!
,
Jul 11
> As per C#2 and C#3 this seems to be inconsistent Why doesn't anybody seem to read comment 5?
,
Aug 13
,
Nov 16
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Jul 9