Comments for mootools's mootools-core  

Hooray!

Yes, IE8 has onchashchange too, but if I just want to know version of Gecko, then these functions and properties are easier to use.

Well, then this is no problem anymore. Maybe a fallback "if" function, for situations with userAgent in some "broken-up" or isn´t given at all.
Just to say it loudly: onhashchange is HTML5 function, so this func. should (I know, only "should") stay in the engine forever.

I agree with Valerio here, these are basically used as browser agent props to help identify browsers in situations where feature detection won't work. So why not use user agent sniffs for it :D.

It's the same problem all over again. Tomorrow they might decide they don't want the function in there any longer, and we're screwed again. User agent is safe, as they wouldn't dare to change it. They can remove functions because they don't care screwing a few thousands developers (they clearly stated it in an email to me), changing the user agent will screw hundreds of thousands of developers, so that's clearly not going to happen.

i think it would return undefined since there would be no function associated with the onhashchange.
Still, IE8 has onhashchange too.

Hello there,

What about to try onhashchange (from firefox 3.6+ in gecko 1.9.2+) this: https://developer.mozilla.org/en/DOM/window.onhashchange
Then there is no need to use UserAgent string, is it?

in fact both ways do the same thing

y hallo thar kind moo

SuperHero!

Hello ;)

hello

Stop spamming! :D

This is because if you use 'readOnly' for example it will use setAttribute, and if you use 'readonly' it uses element.readOnly = ''.
If the toLowerCase() function is used they both (camelCased and lowercased) will work the same (element.property = '').
readOnly is the same case as defaultValue, you would have to add it to this attributes object... (if toLowerCase is not there).
Still doing some tests here, will commit soon... (ill test all the camel cased properties on all major browsers on the set and get property method).

Anutron, thats why i've put that toLowerCase() on the set/get/remove property.
using

setProperty('defaultvalue', 123)

will work ok, but

setProperty('defaultValue', 123)

Wont work... that is the same case as some other properties... ill make some test cases here to analyze this.

Here's a search on the USPTO for the author. No patents. https://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=0&f=S&l=50&TERM1=Diego+Perini&FIELD1=INNM&co1=AND&TERM2=&FIELD2=&d=PTXT

John Resig
Sep 25 2007, 11:56 am

I have another technique that I posted to the list a while back, that
I'll be switching jQuery to. If you attempt to insert into the
document.body before the document is fully loaded, an exception is
thrown. I take advantage of that to determine when the document is
fully loaded. I like that particular technique better because it
actually tells you when you can manipulate the DOM - as opposed to
this scroll thing which may, or may not, correspond to the document
being loaded.
--John

Now should we research to see who cam up with that idea first? Or should we just move on with our lives?

See https://github.com/mootools/mootools-core/commit/2dbd3a1eb2be0c60e2fa8c61cec0697f3404deea for further dicsussion

The opensource world thrives on ideas. Ideas come from everywhere. This, like a million other things, is an example of what I would call "a neat trick" or possibly "a brilliant discovery". I don't want to belittle anyone, their work, or their contributions to the state of the art. But it's absolutely impossible to cite the source of every neat trick or brilliant idea. All ideas come from somewhere, keeping track of who gets the credit just doesn't scale.

MooTools doesn't use many source code comments.
If you really want to know where a certain line of code comes from then you can do a blame on the code to find the original commit message. Hopefully the commit has a nice descriptive comment like f894a59.

Seriously, I don't get what your problem is. This is a method call: A simple call to a method. And for some reason it is possible with it to make sure that the dom has been loaded in Internet Explorer. I was not aware that you can patent a method call. The original code, as you say it, uses "d.documentElement.doScroll('left');" and MooTools used "temp.doScroll('left')" - there is nothing more we integrated from the original code. If its really that easy I now want you to ask for permission and to attribute me when you are using a for loop to iterate over an array with a variable called "i" (example: for(var i = 0; i <= array.length; i++) ) simply because I was the first one in JavaScript to come across this weird behavior (it iterates over every element in an array, oh noes!). Kthxbye.

For the record, Valerio Proietti's own commit:
" - applied this code (https://javascript.nwbox.com/IEContentLoaded/) and ..." https://github.com/mootools/mootools-core/commit/f894a59d2068cbd058853732805048b9d823a10c

Diego Perini's license:
"10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author
to ask for permission."
https://javascript.nwbox.com/IEContentLoaded/GNU_GPL.txt

jQuery, Prototype, Ryan Morr's onDOMReady, and Qooxdoo did the right thing and asked permission or at least gave proper attribution:
(example) // If IE is used, use the trick by Diego Perini // https://javascript.nwbox.com/IEContentLoaded/