WheelEvents, Elliptical Canvas Paths and chrome://inspect Improvements

Published on in Blink, Google Chrome, Last Week, tech. Version: Chrome 31

Last week, 430 authors committed 1,760 changes to the Blink, Chromium, Skia and v8 repositories. This article highlights some of them, up to revision 220870.

Christophe deprecated the returnValue property on all events, and instead properly implemented the property on the onbeforeunload event. He made arguments mandatory on a ton of native methods, and fixed the <select>.remove() method to act as described in DOM4 is no index argument has been passed. Two weeks ago he also implemented the WheelEvent from DOM Level 3.

The preferred and intrinsic width calculations for multiple column layout have been aligned with the specification. Support for ellipses as primary citizens in the world of 2d canvas path segments has been implemented. The change which makes devicePixelRatio include browser zoom has now been enabled by default. Support for the paint-order style for SVG elements has been implemented, as has the object-fit property which aids in maintaining the aspect ratio of replaced contents within its content box.

As for experimental features, the viewport will be reset to its implicit size when @viewport rules at-rules are being dynamically removed. The escape key may now be used to dismiss an active <dialog> window, which have also been made ARIA-aware and are now able to fire close() events. Work on unprefixed CSS Animation also continues, now with the CSSOM part.

Other changes which occurred last week:

Thanks for reading!

5 Responses to “WheelEvents, Elliptical Canvas Paths and chrome://inspect Improvements”

Both comments and pings are currently closed.


September 3, 2013 at 9:33 pm

The pacing in the cast implementation is in relation to TCP pacing, so that slow-start because idle can be avoided for example but not an expert in this

see also http://thread.gmane.org/gmane.linux.network/281740


September 5, 2013 at 9:45 am

Hello Peter, and thank you for your weekly report.

I have a question and perhaps you could help me. I know a Blink bug has been fixed, its SVN revision number is in the ticket. How to know in which version of Blink, Chrome/Chromium canary, dev, beta, stable the fix will be included? In fact, when you have Google Chrome or Chromium, you can’t know on which version of Blink it’s based, right?

Thanks in advance!

Peter Beverloo

September 5, 2013 at 12:34 pm

TOMHTML, if you go to chrome://version/ there’s a row which indicates the Blink version. The number behind the @ is the revision which was used.


September 5, 2013 at 1:12 pm

*A*W*E*S*O*M*E* 🙂 Thank you very much 🙂