Cursor is still pointer when his html element is already removed or not displayed
Reported by
viktoriy...@gmail.com,
Sep 28
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Point the mouse cursor to any button (cursor should become pointer) 2. Click the button (it should disappear, e.g. when another form opens on the button click) What is the expected behavior? Curson should be 'auto' if hovered element is not displayed more What went wrong? Cursor is still pointer but his html element is already removed Cursor becomes 'auto' when user moves mouse a bit Did this work before? Yes Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This bug does not reproduse sometimes. I could not figure out the exact condition
,
Oct 1
Unable to reproduce the issue on reported version #69.0.3497.100 and latest chrome #71.0.3567.0 using Windows 7 and Windows 10 by following below steps. Steps: ===== 1.Launched chrome. 2.Navigated to "https://www.tutorialspoint.com/compiler_design/index.htm". 3.Clicked on "Print" button, observed that the cursor changed from pointer to auto after navigating to next page. Note: Tried with the "PDF" button also but unable to reproduce the issue. Attached screencast for reference. @reporter: Could you please review the screencast and let us know if anything is being missed from our end. Request you to provide a sample file or URL which reproduces the issue so that it would help us for better triaging of the issue. Thanks.!
,
Oct 9
On click "Print" or "PDF" button, the new tab is opening. I've just tried to click "Next page" button and the issue was reproduced. Please see the screencast.
,
Oct 9
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 10
Able to reproduce the issue on chrome version #60.0.3072.0, reported chrome version #69.0.3497.100 and latest canary 71.0.3575.0 on windows 10, Mac10.12.6 and Ubuntu 17.10 by following steps as per comment#3. This is non-regression issue and the behavior is seen from old M-60 builds, hence marking is as untriaged and requesting someone from the dev team to kindly look into the issue. Thanks.!
,
Nov 15
** Mass UI Triage ** Able to reproduce the issue on Win 10, Debian Rodete & Mac OS with chrome #72.0.3610.0 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 30