Click on underline of Google Search link does not open link
Reported by
lapcatso...@gmail.com,
Oct 19
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Open https://www.google.com/search?num=100&q=google+chrome+bug for example. 2. Hover index finger of mouse pointer directly over the underline of a search result link. 3. Click What is the expected behavior? The linked page opens. What went wrong? The linked page does not open. The underline disappears. After that, the link underline appears and disappears as you move the mouse pointer up and down, unlike before. Did this work before? Yes Not sure. Several weeks ago. Chrome version: 70.0.3538.67 Channel: stable OS Version: OS X 10.13.6 Flash Version: This issue doesn't occur in Safari or Firefox on Mac. It took me a long time to find the steps to reproduce. For several weeks now I've been noticing that Google search links just randomly fail to open when I click. Apparently it depended on exactly where my mouse pointer happened to be hovering.
,
Oct 19
,
Oct 19
,
Oct 23
Able to reproduce the issue on mac 10.13.3 using chrome stable #70.0.3538.67 and latest canary #72.0.3588.0. Issue is not seen in OS-Win and OS-Linux. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Oct 28
I couldn't reproduce this on macOS. Is it still reproducible?
,
Nov 9
I can reproduce it as well on both my Mac systems running Chrome 70.0.3538.77. Increasing the font size does indeed help. Thank you for reporting this. I've been noticing this daily over the past few weeks and thought I was going crazy.
,
Nov 12
Anyone who can reproduce this issue, please tell us the detail of your environment. - OS version. e.g. 10.13.6 - Hardware model: e.g. Mac Pro (Late 2013) - Retina display or not. - Page zoom level. Is it reproducible in Incognito window?
,
Nov 12
- OS version: 10.14.1 (18B75) - Hardware model: MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports) - Retina display - Page zoom level: 100% - Is it reproducible in Incognito window? Yes (Note that I'm testing on the results page of www.google.com)
,
Nov 12
The NextAction date has arrived: 2018-11-12
,
Nov 12
I was able to reproduce on this environment: - OS version: 10.13.6 - Hardware model: MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports) - Retina display: Yes - Page zoom level: any - Is it reproducible in Incognito window? Yes
,
Nov 13
- OS version: 10.11.6 (El Capitan) - Hardware model: Mac Pro (Early 2008 -- MacPro3,1) - Retina display? No - Page zoom level: 100% - Is it reproducible in Incognito window? Yes
,
Nov 13
- OS version: 10.14.1 (Mojave) - Hardware model: MacBook Pro (Retina, 15-inch, Mid 2014) - Retina display? Yes - Page zoom level: 100% - Is it reproducible in Incognito window? Yes
,
Nov 14
,
Nov 14
Thank you for the information.
I finally reproduced on my local Mac, and created almost-minimum repro:
<!DOCTYPE html>
<html>
<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head>
<body>
<style>
body{font-size:small;font-family:arial,sans-serif}
h3{font-size:medium;font-weight:normal;margin:0;padding:0; display:inline-block}
.r{display:inline;font-weight:normal;margin:0}
a:hover h3{text-decoration:underline}
a { background:#ccffcc; }
</style>
<div class="rc"><div class="r"><a href="javascript:log('link clicked');alert('Hit');"><h3>Pad See Ew (Thai Stir Fried Noodles) | RecipeTin Eats</h3><br><div style="display:inline-block"><cite>https://www.recipetineats.com › Collections › 15 Minute Meals</cite></div></a>
<pre>
</pre>
<script>
function log(m) {
document.querySelector('pre').textContent += m + '\n';
}
document.querySelector('a').addEventListener('click', e => { log('A: ' + e.target.tagName); });
document.addEventListener('click', e => { log('document: ' + e.target.tagName); });
</script>
Interestingly, 'click' event isn't dispatched on any elements.
,
Nov 14
,
Nov 14
The search side of this bug is
,
Nov 14
er, that was meant to be "the search side of this bug is being looked at by jbrunner@google.com".
,
Nov 14
I observed the same as comment 15, this behavior only reproduces with specific markup constraints. With that in mind, we can tweak the markup of Search results so users no longer experience this on google.com. The change should take effect over the next week. Independently of that, I believe this could continue to be looked at as a general issue with Mac Chrome, as it might also reproduce on other sites that use the same arrangement of HTML and CSS (as unlikely as that may be).
,
Nov 15
The problem is that pointerup and pointerdown goes to different elements and due to a hack that we don't send click events when these two event's targets are beyond an interactive element boundary (i.e. link in this case) then nobody gets the click event instead of their first parent. I believe Google search changes the layout a bit at the current stage that pointerup goes to a different node (i.e the link) and pointerdown goes to a h3. jbrunner@ can you confirm this?
,
Nov 15
I think I might be misunderstanding the question in comment 20, but no, Search isn't manipulating the markup in any unconventional way when the click event fires, or routing the click events to particular elements, or anything like that. As with comment 15, I could reproduce this outside of Search, my repro was minimal, and it includes only HTML and CSS.
<html>
<head>
<style>
*{font-family:arial,sans-serif;font-size:13px;font-style:normal;font-weight: 400;}
.outer{display:inline;}
a{color:rgb(26,13,171);text-decoration:none;}
.title{display:inline-block;font-size:16px;margin: 0px;}
a:hover,a:hover h3.title{text-decoration: underline;}
.inner{display: inline-block;}
.url{color: rgb(0, 102, 33);}
</style>
<body>
<div class="outer">
<a href="https://www.google.com/">
<h3 class="title">Google</h3>
<br>
<div class="inner">
<cite class="url">https://www.google.com/</cite>
</div>
</a>
</div>
</body>
</html>
Also, to clarify my comment 19, when I refer to tweaking the markup of Search results to fix the bug, we will be permanently removing the display:inline; style that is applied to the "outer" <div>. Turns out that it hasn't served any purpose for several years, and without it the issue conveniently goes away.
,
Dec 3
,
Dec 3
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by lapcatso...@gmail.com
, Oct 198.6 MB
8.6 MB View Download