W3C home > Mailing lists > Public > www-style@w3.org > July 2011

Re: [css3-ui] text-overflow: ellipsis and :hover

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Thu, 30 Jun 2011 21:27:27 -0700
Message-ID: <BANLkTinfF6ViuaKOsUzUgGnhHfmZo_NNGg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: robert@ocallahan.org, Philippe Wittenbergh <ph.wittenbergh@l-c-n.com>, www-style list <www-style@w3.org>
On Tue, Jun 28, 2011 at 11:29, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Sun, Jun 26, 2011 at 3:45 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
>> On Sun, Jun 26, 2011 at 3:29 PM, Philippe Wittenbergh
>> <ph.wittenbergh@l-c-n.com> wrote:
>>> What should happen when the user hovers over the ellipsis when the clipped
>>> string is part of a link ? IOW, does the ellipsis become part of the link or
>>> does the 'box' generated by the ellipsis cover the link (and blocks hit
>>> testing on said link) ?
>>>
>>> Implementations disagree with WebKit and IE (tested IE 8) on one side,
>>> Opera and Firefox nightly on the other.
>>
>> More accurately, Firefox simply ignores the ellipsis for the purpose of
>> dispatching mouse events.
>
> This is the best behavior imo, as the ellipsis is "generated content",
> and generated content generally doesn't participate in mouse events
> beyond the interaction pseudoclasses that CSS defines.

Thanks RoC and Tab, I have updated the spec accordingly to explicitly
note that ellipsing must not affect dispatching of pointer events.

http://dev.w3.org/csswg/css3-ui/#text-overflow

Tantek

-- 
http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5
Received on Friday, 1 July 2011 04:28:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT