Re: position: pointer

I added a section to the draft, roughly specifying how to treat carets,
pointers and user agents with no pointing devices attached.


On Tue, Oct 9, 2012 at 1:45 PM, Andrew Thompson <> wrote:

> Logically, wouldn't one also want to add position: caret to cater for
> those people using caret based browsing?
> Or alternatively specify what happens if the browser is in caret mode? If
> one of the use cases for this is hover effects that follow the user's
> current point of interest, that would be the caret not the pointer if a
> caret exists?
> On Oct 9, 2012, at 6:20 AM, Jussi Kalliokoski <>
> wrote:
> As per Brian Kardell's suggestion, and seeing that this might go
> somewhere, I threw together a quick spec draft for the proposal [1].
> Cheers,
> Jussi
> [1]
> On Mon, Oct 8, 2012 at 8:08 PM, Jussi Kalliokoski <
>> wrote:
>> Hi everyone,
>> I wanted to discuss the possibility of adding a new `position` type
>> called `pointer`. I came up with the idea as I was thinking about how
>> limited `title` attribute tooltips are, which made me check out the JS
>> libraries for the purpose, which are crappy as well, and I think JS
>> shouldn't be needed for "simple" positioning of elements like this (there
>> may be a few cycles to save here as well). The idea is pretty simple, it
>> works kinda like absolute or fixed position (in that the element is
>> floating), but the given coordinates are relative to the main pointer
>> position.
>> This would let you make tooltips in pure CSS and HTML (not to mention
>> that you could recreate those stars flying around the mouse from the 90s
>> with just CSS and HTML ;). I made a small demo [1] [2] to give a better
>> picture of what I mean. The actual demo uses a silly JS shim, and I think
>> the smoothness speaks for itself about how unsuitable JS is for this kind
>> of functionality.
>> Looking forward to feedback!
>> Cheers,
>> Jussi
>> [1] (code)
>> [2] (result)

Received on Friday, 12 October 2012 16:32:44 UTC