Issue with the example for Element.contains(). Fixes #2147
Noticed that there's no $uid dependency in Browser.js, moved to Element.js. Removed $uid in favor of Slick.uidOf. PASSED: IE6-9; FFx 3-5, 8, 10; Opera 11; Safari 5; Chrome latest
Fix #2134 merge specs submodule
Conflicts: .gitignore .gitmodules
Updated old spec.
This ensure specs work for 1.2 testing. PASSED: IE6-9, Safari 5, Chrome latest, Opera 11, FFx 3-5, 8, 10
Added spec for button.set('type', 'button')
Webkit bug: https://bugs.webkit.org/show_bug.cgi?id=14439 prevents button.type = 'button' from working as expected. Current solution is to use setAttribute. This fix adds propertySetter.type with setAttribute but only for webkit.
Added Specs for Element.erase.
Fix #2100. Element.erase caused unexpected values for the attributes
Removed unnecessary Element.Properties.class and opted to use propertySetter and getter. Adding for condition to set the value to '' instead of null (IE would set to 'null'). Refactored setProperty. Now much simpler. Checks for propertySetter and assumes it'll take responsibility in cleaning up the value (and to set it). Still removeAttribute if no setter, and value is null. Passes all specs, and therefore, it's backwards compatible. PASSED: IE6-9, FFx 3-5, 8, 10, Chrome latest, Safari 5, Opera 11.
… the unexpected results. Added a feature detect if the browser sets 'null' instead of null in the attribute. Added a `Element.Property` for class. TESTED: Opera 11, Safari 5, Firefox 3-5, 8, 10, Chrome latest, IE6-9.
…eleave native support.
…leave Fix #2089. Feature detect for mouseenter and (assume) mouseleave.
TESTED: IE6-9, Chrome latest, Firefox 3-5, 8, 10, Opera 11, Safari 5 Using Element.Delegation.html.
Refactoring Element.Event specs
Fix #2085 ie8 specs fail
TESTED (green): IE6-9, FFx3-5, Opera 11, Safari 5, Chrome dev IE8 and IE9 require the fireEvent to manually bound. <IE8 just saves a copy prior to augmenting. I tried to keep the code together, but IE didn't let up.