Limiting -khtml- and -apple- prefixes, and location.ancestorOrigins
Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 20
882 revisions landed in Chromium’s repository last week and 667 in WebKit’s. Highlights include removal of support for the -khtml- and -apple- CSS vendor prefixes in Chromium, and the new location.ancestorOrigins() method.
Work on Device Emulation in Web Inspector is continuing and now also supports dimension wrapping to mimic orientation changes, and a “fit to width” option which will inherit the browser window’s dimensions as the device’s resolution. Lines having a breakpoint will now show line numbers and the vertical timeline overview now shows the wall time.
Support for -khtml- and -apple- properties has been removed for most WebKit ports, including Chromium, after previous attempts failed due to compatibility issues. Background sizes are now correct if the page is zoomed out, the default box-shadow color now defaults to the element’s “color” property, the viewport-relative CSS units now work for Replaced objects (such as images) and the -webkit-image-set CSS property was enabled for the Chromium port.
Split over a number of commits, Avi has renamed Chromium’s TabContents class to WebContentsImpl.
Other changes which occurred last week:
- The backingStorePixelRatio property has been added to 2D Canvas contexts.
- Microsoft’s Grid Layout tests have now been integrated in WebKit as well.
- WebKit’s Microdata’s property collection implementation now features caching.
- Implementation of the Encrypted Media Extensions API started in WebKit.
- The new UI for date input types has been enabled for Chromium.
- Jocelyn Turcotte now is a WebKit Reviewer, congratulations!
- Ten percent of Chrome uses will be subject to the SPDY/3 experiment.
- Extension APIs can now be limited to certain release channels of Chromium.
- Full-text regular expression search is now available on chrome://sync.
- Pepper-based Flash is now enabled by default for Windows 8 Metro builds.
And that’ll be all :). Maybe see you at the WebKit’s Contributors Meeting!