Issue metadata
Sign in to add a comment
|
Minimize, Restore, and Close buttons on Chrome browser window do not respond to touch
Reported by
mythmast...@gmail.com,
Oct 9
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open a Chrome browser window on a touch-screen device. 2. Use the touch screen to tap the Minimize, Restore, and/or Close button. 3. Observe. What is the expected behavior? The browser should be minimized, restored to a window/full screen depending on the previous window state, or closed. What went wrong? The buttons do not respond to touch at all. They are not highlighted (the Close button does not turn red when tapped, the others do not change to a lighter back ground), nor do they function except with a mouse click. The window remains the same size. Did this work before? Yes Unknown. I know this worked as of 6 months ago at least, but beyond that I haven't kept a record. Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.3 Flash Version: The browser's top bar (browser top chrome, I believe?) still functions normally in regard to touch (tabs can be closed, opened, and dragged, and the window can be dragged about, made full screen, etc.) in all other aspects that I can tell. In regard to the issue, I have tried tapping multiple times, moving where I am tapping, and generally trying to make sure I was not missing the area/hitbox (? I think I'm using that term correctly), but I have confirmed that it is not an issue with my touch screen (The buttons behave as expected in Firefox and in other programs concerning touch, for instance).
,
Oct 10
Unable to reproduce the issue on reported chrome version #69.0.3497.100 and latest chrome 71.0.3575.0 using Windows 10 Surface pro by following below steps. Steps: ===== 1.Launched chrome. 2.Navigated to "www.google.com" and tapped on minimize, maximize and close button using touchscreen. 3.Observed that minimize, maximize and close button worked correctly. Attached screencast for reference. @reporter: Could you please review attached screencast and let us know if anything is being missed here. Request you to retry the issue by creating a new person without any apps and extensions, reset all flags to default on latest chrome and let us know if the issue still persists. Thanks.!
,
Oct 11
#2: Well, I feel bad about not checking this out fully. You are absolutely right that a new guest profile in Chrome responds correctly to touch events. I am using the following theme, https://chrome.google.com/webstore/detail/yulia-brodskaya/jlgdloilieclkegafohackmhffbmdpko, which does change the above-mentioned buttons (but the design is completely worth it!). I have attached an image of both widows (the lower one, as a guest, works fine with touch, but the upper one, with the different style of buttons, does not). Perhaps the theme is interfering with the normal operation?
,
Oct 11
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
,
Oct 11
Unable to reproduce the issue as per comment#3 on reported chrome version 69.0.3497.100 using Windows 10 Surface Pro, observed that minimize, maximize and close button worked correctly. Attached screencast for reference. Hence removing Needs-bisect label and requesting someone from UI>Browser>Themes team to look into the issue. Thanks.!
,
Oct 12
#5: So, I ran a more complete test of this, and it definitely is this theme (or theme style, template, etc. that is causing this). Looking at your screencast, it seems that Windows 10 displays the buttons differently than in Windows 8.1, which is the OS in which this bug is taking place for me. If you look at my screenshot in comment #3, you see that the buttons have no space between them, have rounded corners, and are smaller. In your screecast, running Windows 10, the buttons are larger, have sharp corners, and have a different background. Perhaps this is an issue unique to Windows 8.1?
,
Oct 18
Can someone attempt to reproduce this in a Windows 8.1 environment? I'm reasonably sure that this has something to do with the issue, but I only have access to one computer.
,
Nov 14
As per comment #7, it seems the issue is specific to Windows 8.1 environment. As the test team doesn't have a Windows 8.1 touchscreen device to triage the issue further from our end. Hence, adding label TE-Hardware-Dependency. Thanks...!! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 10