…the onpropertychange event since size calculation is not accurate during that event and it triggers an onresize event anyway; also work around a weird error thrown when removing the length-calc element from what should be its parent but sometimes isn't.
…errors in some IE versions like the spoon.net IE6. Suggested by Bryan Elliott (@fordiman on Twitter).
… consistency, and let the setting of the className trigger a propertychange update rather than manually calling it a second time.
…he beginning of an update; this allows the changed method to handle tracking itself rather than relying on a side-effect from another method, resulting in more accurate change tracking. Fixes hovering when the unhovered state has no css3 styles.
…t it's going to support natively
…han invoking a full destroy on all elements. This prevents the flash of unstyled elements while leaving the page before the next page loads.
…hey do the same thing for every renderer
…o it is sharp
…mg is set to transparent opacity and rendered as a top layer.
…. Fixes issue #74.
…rder-collapse is 'collapse', to match other browsers.
…ng them onbeforeunload
…error when uncompressed, and reduce code size. Add testcase.
…o avoid positioning errors and to honor the browser's settings for printing backgrounds etc.
…caller already gets cached. (3) Don't use a regexp to parse the value. (4) Use PIE.CSS_PREFIX.
…ugly artifacts when non-px units are used, fixes issue #63.
1) Make the root renderer check all its sub-renderers' isActive state, rather than all the styleInfos, to determine if the main box should be created; this prevents the css3-container from being created and then not getting anything put in it. 2) Prevent the background and border StyleInfo objects from modifying the background/border runtimeStyle if that runtimeStyle has not been modified previously; also don't worry about resetting the border-style as that never gets modified when hiding the border. 3) Wrap several of the StyleInfo methods so that their return values are cached over the course of an update; gives a decent speed bump, especially now that isActive is called more often (see #1) 4) Move the attachment of event handlers down after the first call to update(); this prevents the changes to the element that occur during rendering from triggering update checks. 5) When handling onresize/onmove events, quit early if the element's bounds have not been previously queried; this prevents the extra loops which were firing after all the elements were initted when those elements have no initial CSS3 rendering.
…o it spans across instances rather than just being for the current instance.
…e BorderRenderer is active
…d by a -pie-lazy-init property, and turned off by default. 2) Optimize the case where an element has no CSS3 styling in its initial state, by preventing any queries to getBoundingClientRect which would invoke a reflow. 3) Fix positioning of the rendering element when there was initially no CSS3 rendering but it gained rendering on hover/class change/etc.