Main Area and Open Discussion > General Software Discussion

Aren't all _on_ events JavaScript?

(1/2) > >>

barney:
Folk,

I have a client/student who swears she has seen on events, e.g., onBlur, onClick, onMouseOver, and the like, that are [X]HTML events, not JavaScript.

I keep telling her that they are all JavaScript and do not exist in any of the HTML iterations.

However, I have been unable, to date, to find any concrete statement to that effect.

Her argument is that if you don't have to enclose the event in script tags, it ain't JS.  Her favourite argument is adding the onLoad to the body HTML element.  I'd really like to find something to refute that concept.

Can any of you point me to some source that will unequivocally show her the truth of my assertions  :).  Or prove me wrong, for that matter :o.

mouser:
im not sure of exactly how the terminology would be used, but my understanding is that all of these events trigger javascript.
the onLoad element for html body, is explicitly designed to run JAVASCRIPT -- that you dont have to specify that javascript in a <script> block is irrelevant, it's still executing a javascript statement.

barney:
That's my understanding as well ... but I cannot, for the life of me, find anything that just flat says it outright.  This gal is pretty good at learning & utilizing Web scripts, but she's convinced that some on events are built into HTML, and I've not been able to dissuade her of that notion.

I'm fearful that it will come back to bite her when someone comes along with a JS-disabled browser, or something like Firefox with the NoScript extension.  My thought is that if I can find some documentation to support that these events are strictly JS, then she'll be more amenable to adjusting some of her page scripts.

However, in not even you are aware of such docs, chances seem to border on slim to none  :(.  Guess the only viable alternative is to get her to disable JS in her browser, then visit her own pages, but I'm not certain even that will convince her  :-\.

mouser:
get her to disable JS in her browser, then visit her own pages, but I'm not certain even that will convince her  undecided.
--- End quote ---

anyone designing web pages using such events needs to do this no matter what, so this shouldnt even be an issue -- she needs to try this.
the noscript addon for firefox is good for temporarily disabling javascript, etc.

and any page that requires javascript should display some warning to the user when their javascript is disabled.

barney:
That, sir, is the conundrum.  You know that.  I know that.  She don' know dat, and is extremely reluctant to be convinced, since she can use some JS events - e.g., onLoad, onBlur, onFocus - w/o script tags.  I've been loathe to try to force her, but think that's about the only option left, sans specific documentation.

 ;) This is actually more onerous in that I'm not getting paid for the training ... if she were paying for it, she'd be a lot more likely to attend my warnings  :P.

Navigation

[0] Message Index

[#] Next page