Oh, by the way, this is what will eventually drive Aria/A11y implementations, this is to aid implementors be compliant with specifications about applications for the web in environments where it is needed to meet the requirements for visual or impaired disabilities or other kind of difficulties in typing or well you know...the list grows.
This will hopefully let us all push in an effort to extend the usability of our products and probably the audience too driven by these fact. Remember that Google is, in practice, a blind user visiting your page, it will hardly see any image or video, Google is also 'deaf' so he can't hear your beautiful music, the content is king then... ;-) Much of the software we write will be soon obsoleted by more capable browsers, we are just temporarily working around/overcome unusable parts of them (hope so!) Diego On 10 Gen, 17:15, Diego Perini <diego.per...@gmail.com> wrote: > Daniel, > click events can be triggered in various ways, more generally, events > should be allowed to be triggered by any means of device, a keyboard, > a mouse, a sensitive tablet/surface, a touch screen and so on and even > by voice and manyother means. > > I am scary to even say that seems Microsoft has the best > implementation for what is regarding Activation (I just mean the event > hooks exists, nothing else OK?). > > What you are touching/looking@ is the Activation Model, it is the way > to be really device independent by using a different set of events (on > IE). > > @Dave, I wouldn't make my assumptions a statement, but yes everything > you know/said above could/should be replaced by using activation > events, tabbing to a link for example (just for IE) could be > intercepted by just using "onactivate" event to be sure to catch any > means of activating that link and on any device, be it by keyboard, > mouse, touch or whatever other input aided device. > > I will point out that (on IE) both "onactivate" and "ondeactivate" > exists and have related pairs "onbeforeactivate" and > "onbeforedeactivate" which fire even earlier in the same chain. If you > think to it you can also intercept programmatically fired events (for > example the ones you can invoke from javascript code .submit() .click > () .foucs() .blur()). > > I would really like you have a look at my: > http://github.com/NWEvents > project there you will find some example to understand what these > events are for (again on IE) and what I used them for. ;-) > > For other browsers, the ones following the W3C Event Model, the > "capture" phase is a good replacement to obtain a cross-browser > helper. However it seems there are already tracks of this Activation > model both in DOM Level 3 Events and in most browsers (DOMActivate/ > DOmFocusIn/DOMFocusOut events has been working for some time now). > > Let me know if I can be of help. > > Cheers, > > Diego > > On 9 Gen, 20:11, Daniel Friesen <nadir.seen.f...@gmail.com> wrote: > > > Ugh... I was under the impression that click events only fire when you > > click on something. > > > Aye, activate is supposed to fire in all those cases as well. Click's > > current behavior now seams to really be activate in a confusingly named > > guise. > > > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] > > > Dave Methvin wrote: > > >> Activate basically behaves the exact same as a href on an <a> does. > > > > Sorry I'm still not understanding the difference. The href is an > > > attribute of the link, not an event. It sounded like activate was an > > > event. > > > > AFAIK click is fired by the browser in three cases: when the user > > > clicks the link, when the link has focus and the user presses Enter, > > > or when the link has an accessKey attribute and the user types that > > > accessKey. Does activate fire in all those cases as well? > > > > Do you have some reference urls that explain it all?
-- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
