> > > Since this is effectively capturing where the user's attention is being > > spent (the click event I mean), should you also define the other set of > > events of interest as well? > > <a href="..." on-click-notify="myattention.org/dierken" > > on-hover-notify="myattention.org/dierken" > > on-copy-notify="myattention.org/dierken">Wicked Cool Stuff Here</a> > > This would be way too much. On copy/hover/click? You'd want this? > I wouldn't. Companies would definitely want this. > > You anticipated something that will happen. Not now, not in this > specification. It's too much at once. Everything must be > taken slowly, > step by step. First step is ping=. > True - but if you use a name that is descriptive, the future extensions would be easier to migrate into.
- Re: [whatwg] <a href=""... dolphinling
- Re: [whatwg] <a href="&... Ian Hickson
- Re: [whatwg] <a href=&qu... dolphinling
- Re: [whatwg] <a href="&... ROBO Design
- Re: [whatwg] <a href="" ping=""... S. Mike Dierken
- Re: [whatwg] <a href="" ping=""... dolphinling
- Re: [whatwg] <a href="" ping=""... S. Mike Dierken
- Re: [whatwg] <a href="" ping="... Jasper Bryant-Greene
- Re: [whatwg] <a href="" ping=&q... S. Mike Dierken
- Re: [whatwg] <a href="" ping="... ROBO Design
- Re: [whatwg] <a href="" ping=&q... S. Mike Dierken
- Re: [whatwg] <a href="" ping="... Mike Dierken
- Re: [whatwg] <a href="" ping=&q... Gavin Sharp
- Re: [whatwg] <a href="" pin... Mike Dierken
- Re: [whatwg] <a href="" ping=&q... ROBO Design
- Re: [whatwg] <a href="" pin... Ian Hickson
- Re: [whatwg] <a href=""... Lachlan Hunt
- Re: [whatwg] <a href="&... Ian Hickson
- Re: [whatwg] <a href=&qu... ROBO Design
- Re: [whatwg] <a href=&qu... Ian Hickson
- Re: [whatwg] <a href=&qu... Lachlan Hunt
