::after tag not rendering clickable images/area - works in Safari, Firefox, IE
Reported by
matthew_...@starkey.com,
Dec 9 2016
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36 Steps to reproduce the problem: 1. create li group with a tag in li elements 2. setup ::after for a tag with certain class that has background (ass seen in screen capture attached) 3. Click on the link - compare to other browsers What is the expected behavior? I am expecting that when I click on the hyperlink where I see the image, that the hyperlink action for navigation is executed What went wrong? no navigation occurred, and no detection of this being a navigation element is occurring on Chrome - though when compared to 3 other browsers it works successfully on those browsers Did this work before? No Chrome version: 55.0.2883.75 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0 In the example image there are two ::after background url images, I can limit to just one, and either way this will still not grab the area of the displayed image and turn it into a hyperlink/navigation link.
,
Dec 12 2016
,
Dec 12 2016
matthew@ Thanks for filing this issue, Could you please provide a sample URL of the webpage or sample test case to check this issue from chrome TE end. Thanks!
,
Dec 12 2016
,
Dec 15 2016
Is anything else needed? The HTML example attached I was able to reproduce, but I am checking if this was not working for a proper example. When using that HTML in chrome, clicking the google image does nothing. Any other browser it will properly navigate to the anchor tag href URL.
,
Dec 23 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 20 2017
Able to reproduce on Windows 10, Ubuntu 14.04 and Mac OS 10.11.5 using chrome latest stable M55-55.0.2883.87. Bisect Information: ===================== Good build: 44.0.2373.0 Bad Build : 44.0.2375.0 Blink Log URL: https://chromium.googlesource.com/chromium/blink/+log/b0fde00..62622f5 From the above log suspecting below change Review URL: https://codereview.chromium.org/1087893004 pdr@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks!
,
Jan 20 2017
Thanks for filing this and creating a small testcase. This is a regression from https://chromium.googlesource.com/chromium/blink/+/d5129e55453ac9c8d3dcfee263363b48b2f3bf1b
,
Feb 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 16 2018
Still broken. The fix I made a while back for pseudo elements doesn't appear to have fixed this one.
,
Feb 16 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by ajha@chromium.org
, Dec 12 2016