Re: HTML, following implementations, treats active state and :active-matching as different things

Forwarding another message from Hixie:

> On Wed, 16 Feb 2011, Tab Atkins Jr. wrote:
>> The *sole* problem is that Selectors uses the word "activate" in a
>> different way than HTML does.  (Specifically, we don't define what
>> "activate" means, but HTML does, and it's a different meaning than what
>> you want for :active.)
>
> I've changed the HTML spec to just say that "activate" means something
> different just for the purposes of :active. It looks weird, but it means
> that we can argue it's not conflicting, so hopefully that puts this issue
> behind us.

For reference, the relevant HTML spec text can be found at
<http://www.whatwg.org/specs/web-apps/current-work/complete/links.html#selector-active>.

~TJ

Received on Wednesday, 16 February 2011 20:25:38 UTC