https://crbug.com/853726
Reported by
shrade...@nomissoft.com,
Nov 21
|
||||
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: See the narrative for issue 853726 and comments, in particular comment 3 at https://crbug.com/853726 What is the expected behavior? Click on link (clicked link turns green), arrive at linked page, press back. The last active link (focus) should still remain green for being focus and active (but as of current turns red as only being visited but not active or focus). What went wrong? When clicking on a link and returning via the back function, the focus gets lost. Repeat of comment 3 in old issue: Page (see example attached) needs to set visited and focus colours differently: A:visited { color:red;text-decoration:none:font-weight:bold; } A:active { color:green;text-decoration:none;font-weight:bold; } A:focus { color:green;text-decoration:none;font-weight:bold; } Now click on "Bug List" link in the example, link (because it becomes focus and active) turns green, the new page (the list of chromium bugs) is called and displayed. Now go back, the link colour has changed to red (visited) but not to green (focus, active). If you then try to tab to the correct link, the first tab "greens" the first "specific bug" link, only the second tab then the previously active "Bug list" link. This second observation also highlights that the correct keyboard input field (focus) has been lost. Did this work before? No Chrome version: 69.0.3497.100 Channel: n/a OS Version: 6.3 Flash Version: I'd like to reopen the old issue 853726 but don't find the option to do so, hence I need to re-issue the bug report as a new issue. I ask however to re-open the issue 853726 and merge the two bug reports.
,
Nov 23
Able to reproduce the issue on reported chrome version 69.0.3497.100 also on latest chrome 72.0.3618.0 using Mac 10.14.0, Ubuntu 17.10 and Windows 10. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Nov 23
++ Correcting the above comment #2. unexpectedly deleted above comment #3 and adding OS labels.
,
Nov 29
|
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, Nov 21