New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 775579 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Link reminds clickable even it's clipped by overflow:hidden

Reported by konr...@gmail.com, Oct 17 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Resize preview window in order to see ellipsis.
2. Hover over ellipsis (the space between right border and the last ellipse) with your mouse pointer (it should get cursor: pointer;)
3. You should be able to click on link.

What is the expected behavior?
The expected behavior is you should not be able to click on link element, i.e. the link should be clipped.

What went wrong?
You can click on link even if it is clipped by overflow: hidden;

Did this work before? N/A 

Does this work in other browsers? No
 This bug can be reproduced in FF, but work correctly in IE11

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

link to JSFiddle in order to reproduce and see the BUG:
https://jsfiddle.net/Konrud/xntmjqmz/
 
Labels: Needs-Triage-M61

Comment 2 by shend@chromium.org, Oct 17 2017

Components: -Blink>CSS Blink>Layout Blink>Input
Status: Untriaged (was: Unconfirmed)
Can reproduce on 63.0.3236.7 (Official Build) dev (64-bit).
Not sure where this bug should go, redirecting to the input and layout team. If this is actually a style issue, please add back the Blink>CSS component.
The overflow: hidden spec talks about scrolling. It doesn't mention not being able to click.
https://drafts.csswg.org/css-overflow-3/#propdef-overflow

Comment 4 by e...@chromium.org, Oct 17 2017

Components: -Blink>Input
Owner: tabatkins@chromium.org
Status: Assigned (was: Untriaged)
Regardless of the desired behavior (which is unclear and not defined in the spec) our behavior here seems wrong in that we do not threat the ellipsis itself as a click target but the space after it.

We should request input from the CSSWG and update our implementation to match.

Over to Tab for spec input.

Sign in to add a comment