… longer uses any Blur filter, instead it now uses a radial gradient from opaque to transparent with the undocumented 'gradienttitle' fill type so it follows the rounded box shape. There is no longer any lag with initial rendering, updating size, or scrolling the page. It also gives better control over the size of the blur gradient so it more accurately matches the blur metrics of other browsers in most cases.
…yle is not "none".
…sking currentStyle whether the element is visible; fixes problem where the VML would disappear in IE6 after initial rendering, because the way we hide borders in IE6 is by setting visibility:hidden on the outer element.
…3 features, with simple UI for enabling/disabling and tweaking parameters. This will likely be used on the css3pie.com main page.
…kground and border colors from transparent to the default
…aphy.com/experiment/circles/solarsystem/ with slight modifications
…ment position:fixed so it stays aligned
…mprovement. Also renamed StyleBase -> StyleInfoBase.
…lement's visibility was changed (via visibility or display css props) and where they would be rendered even if the element was initially hidden via visibility:hidden.
… to use getBoundingClientRect rather than offsetLeft/Top/etc. -- this prevents situations where the element's position relative to its positioning container actually changes but its offsetLeft/Top stay the same. Closes #15.
…his is not required to make onmove/onresize events fire after all. Tests still appear to function properly. Fixes the margin collapsing issue described in issue #14." Turns out hasLayout is indeed required in order for onmove and onresize events to fire. My tests were faulty because the window's onresize handler was firing. This reverts commit 182fcb0.
…ly failing. Also set position:relative on test 2 to prevent rendering element from going behind its parent background.
…kage to prevent error
…ot required to make onmove/onresize events fire after all. Tests still appear to function properly. Fixes the margin collapsing issue described in issue #14.
… when positioning the main css3-container.
…g oddly positioned