This update discusses the 1,522 WebKit and 2,131 Chromium changes that landed in the past two weeks, totaling up to 3,653 changes.
Chromium updated the libvpx library to include support for an early version of the VP9 decoder, the successor of the VP8 codec that’s currently used by WebM. Furthermore, though still behind a flag (also available in about:flags), WebM files containing audio streams using the Opus codec are now supported as well.
Support has been added for the “widows”, “orphans” CSS properties, as well as for the “ruby-position” property. The text-orientation property now supports the “sideways-right” value and text decorations will now work correctly when text-combine is being used as well. Furthermore, out-of-range values will now be clamped to values the supported range. Applying SVG filters to elements through the url() syntax will now work even when the filter isn’t available yet, and CSS Exclusions’ shape-inside is now supported for multiple-segment polygons.
Elliot moved generated content in :before and :after CSS pseudo-elements to the DOM, which also means that supporting animations and transitions on them is close. The Shadow DOM’s ShadowRoot constructor is gone, XMLHttpRequests for blob data will now set their Content-Type header accordingly and status events will now be fired for <link rel=prerender> elements. The Web Audio API now supports an offline audio context and the ::cue pseudo-element for video elements now is supported as well.
Support for in-band text tracks is now available on the Mac port, and plumbing has been added to allow deferring displaying of text tracks to the embedder.
This update talks about the 690 WebKit commits and 1039 Chromium commits which landed last week.
A canvas’ 2D context’s globalCompositeOperation property now also accepts the various blending modes. The unpause() method on a MediaController object is now supported. Removing non-existent cues from a text track will raise an exception, and a media element’s textTracks property will now reflect the associated <track> element.
The :read-only CSS pseudo-class has been updated to work with date and time input types as well. The -webkit-mask-attachment property has been removed and the masking size has been added to the -webkit-mask shorthand. WebKit’s Multiple Column implementation now accepts “none” as the value for column-span rather than just one, and tables have started respecting the max-height property.
As for experimental features, Julien is continuing his work to implement the CSS Grid Layout Module in WebKit, and landedseveralmore patches. Dave also landed another patch for the new Multiple Column implementation, and CSS Shaders’ input colors will now be clamped before being blended. More tests have been added for the CSS Device Adaptation implementation, and values provided through the meta tag won’t be clamped anymore.
Other changes that occurred last week:
An OpenCL-based implementation of several filter effects has been added.
A basic implementation of the Web Audio API’s MediaStreamAudioDestinationNode landed.
Printing in a custom font on a <canvas> object can now also fall-back to other fonts if it’s unavailable.
Web Inspector has enabled JSON previews for text/html XMLHttpRequests. Line numbers in the timeline panel are now searchable and pressing the Ctrl+End shortcut in the code editor will bring you to the last character again.
The feature flag for the DAP Proximity Events feature landed. A few other potentially upcoming features were discussed on the WebKit mailing lists last week as well, namely using OpenCL for filters, Pointer Events, the Screen Orientation API and adding the <main> element.
Other changes that occurred last week:
Some minor progress was made in hooking up the Fullscreen API for Android.
James started working on Resource Timing tests, in W3C style so they can be submitted.
The EFL port added support for using the ATK library for Accessibility support.
Chromium for Mac switched to WebKit’s TCMalloc, improving DOM modification performance by up to 15%.
Chromium enabled support for the datalist UI for datetime and datetime-local input fields.
Last week yielded 932 WebKit commits and 1,111 Chromium commits, totaling up to 2,043 changes.
Within Web Inspector, several overrides have been moved out of the Settings panel. The Apple port now features a dock button in the top-right corner of the Web Inspector window. A checkbox has been added for toggling a visible FPS counter on the page, and a warning will now be shown in the console when invalid sandbox flags are encountered.
The feature flags for CSS Hierarchies have been removed again. Tab made parsing of the @charset rule stricter, the algorithm used for positioning <track> subtitles has been updated to better support multiple lines and the wrap-margin/padding properties have been renamed to shape-margin/padding. Various basic shapes, such as polygons, circles, rectangles and ellipses are now animatable with themselves, which can be used on both the clip-path and CSS Exclusions’ shape-inside properties.
Parsing for the text-align-last CSS property has landed. WebKit has also been updated to return the right value for <legend>.form, which should be in sync with an optional ancestor fieldset element. For Chromium, autocomplete=off will now be ignored when filling in an automatically created password. Finally, sevenpseudoclasseswereupdatedtoproperly distribute in shadow trees.
1,652 changes landed to the projects last week, 889 to Chromium’s repository and 763 to WebKit’s. The v8 project received 77 commits, quite a few of which were related to implementing the new Object.observe() feature.
Within v8, Adam, Rafael and Andreas are working on implementing Object.observe(), variouscommitsforwhichweremade. While the implementation isn’t complete yet, it can be enabled by passing the –harmony-observation to v8. ECMAScript 6’s Map and Set collections now include the size and clear properties and JSON.stringify() is now better at handling proxies.
Canvas images reprojected using the -webkit-canvas() CSS function will now use the full backing store rather than the scaled ones, which improves quality on many mobile devices. Support for the “desktop-width” directive in the meta viewport element has been removed. Also newly supported are date pickers for <input type=month> and <input type=week>, and Skia is now able to use reference URL filters on composited layers.
It’s now possible to show a list of tracks available for media elements, an UI for which will be implemented soon. A touchEvent’s client{X,Y} attributes will have the right scrolling adjustments applied, proper escaping of quotes will now be applied in various HTML extension methods (String.prototype.anchor, link, etc) for JavaScriptCore and getUserMedia() will now throw a TypeError instead of a DOMException.
The Content Security Policy DOM implementation has been updated to match the specification. The interface is now called document.securityPolicy and various methods are now exposed as read-only properties.
Today’s update talks about the 925 Chromium changes and 677 WebKit changes made during the past week.
The version number Google Chrome will be using is now equal to the value of a British Pony, as carefully described by Anthony. As usual, there’s a label for a rough overview of the changes that went in to Chrome 24.
Quite a few performance improvements went in last week. Elliott improved performance of getElementsByTagName, among various other tests, by several percentages. Eric has been working on addressing RoboHornet(Pro) issues: rendering tables with column groups now is twice as fast, devirtualizing first- and lastChild() yielded another 30% speedup, and another 35% improvement which lowers the total test run-time from 8.2 seconds to just 5.3!
WebKit’s Content Security Policy implementation will now listen to unprefixed Content-Security-Policy headers included in the HTTP response. This header will be preferred to X-WebKit-CSP, which still must be used in case you’re supplying CSP 1.1 features to the browser. Development of the cross-site scripting protection has been picked up again. Malformed headers will now be reported, and report URLs can now be defined in the X-XSS-Protection header.
Other changes which occurred last week:
All code related to the experimental Undo Manager API has been removed, as it went unmaintained.
Touch adjustment scoring now normalizes with respect to the maximum possible overlap area.
Apple enabled support for sub-pixel layout positioning on the Mac port.
A lot has happened again last week, and this update covers the 739 WebKit and 995 Chromium commits which have occurred since. Highlights are the @host rule for Shadow DOM and resolution media queries.
A new extension API just landed in Chromium which adds support for capturing the contents of a tab through WebRTC. The API, tabCapture.capture(), works similar to getUserMedia() and also makes a LocalMediaStream JavaScript object available.
Resources using data: URIs in Web Inspector will now be trimmed at a reasonable point, increasing readability. Stylesheets will now also be reloaded when any in-use SASS resource has been saved in the Sources panel.
A number of create*() methods of the Web Audio API’s AudioContext object have been renamed to match the latest specification. Pasted fragments will now always be parsed as HTML, even on XHTML pages, and the default action for the “dragover” event now prevents dropping when dragging files.
Kenneth added support for the “resolution” media query, most useful when used in conjunction with the dppx unit, and a feature flag for implementing features from CSS Device Adaption did land as well. John Mellor’s Text Autosizing implementation got the interest of Samsung, who are working on implementing the API in WebKit2, and timeout support for XMLHttpRequests has been implemented as well. Finally, all the compositing operators for CSS Shaders are now supported, with the exception of “destination” and “lighter”.
This update covers 1,921 Chromium changes and 1,426 WebKit changes which happened over the past two weeks, totaling up at 3,347 changes. Highlights are support for conditional CSS, support for polygonal shapes in CSS Exclusions and support for Shadow DOM, now shipping with Chrome.
Chromium has enabled both Shadow DOM and scoped stylesheets by default, and both features which will ship with Chrome 24. This also applies to MathML, which has been worked on by David Barton in the past year.
Web Inspector now supports styling console message output by using the %c modifier, together with a string of defined styles in the second parameter. HTML as part of XMLHttpRequest responses will now be previewed in the Network Panel, and hovering over console messages will now highlight them.
Seven nodes of the Web Audio API have been renamed to be more consistent with other node types. A “force” parameter has been added to the DOMTokenList’s toggle() method, Content Security Policies now support paths at file-level granularity and text controls were given the setRangeText() method.
Sorry for the recent lack of updates, I’ve been really busy. This update discusses everything until the 24th of September, so two weeks, not including last week. Early next week I’ll publish an article covering last and this week, to get you fully up to date again.
In Web Inspector’s Style panel, the relevant selector that causes a rule to be applied to a certain element will now be highlighted. The XMLHttpRequest Replay feature has been added to the Network Panel, search and filtering features are now available in the Timeline panel and all named flows can now be displayed in the CSS Named Flows drawer.
Support for drawing dashed lines in the 2D Canvas APIs according to the specification landed, and introduced the getLineDash and setLineDash methods, and the lineDashOffset attribute. The prefixed version of Blob.slice() has been removed, and Chromium has removed support for the prefixed postMessage method. SVG’s appendItem method on path segment list has been sped up from linear to constant time. Support for creating a Shadow Root on replaced elements has been removed for now and CSS Region’s getRegionFlowRanges method on Elements has been implemented.
David Barton updated all of MathML’s rendering to be based on the Flexible Box module, simplifying the code significantly. Over the past number of months, he’s done quite a lot of work on improving WebKit’s implementation of MathML, which may ship with Chrome 24.
WebKit’s Content Security Policy implementation now features supports for paths in directives’ values. Blocked inline scripts will cause Web Inspector to pause, ignored directives due to non-ASCII values will now generate warnings and JavaScriptCore’s description when blocking eval() has been clarified.
Other changes which occurred in the last two weeks:
A gender-neutral version of the “webkit-patch land-cowboy” has been added: land-cowhand.
This update discusses the 1,305 WebKit changes up to revision 128,016, and the 1,707 Chromium changes up to revision 155668, and is therefore covering the last two weeks.
Support for the overflow-wrap property has been added, which is a new property to which word-wrap is a shorthand. Within the calc() function, expressions using the “em” unit will now zoom correctly and it’s now possible to use CSS Variables within expressions, assuming support for both is available in your build. Robert fixed yet another CSS 2.1 issue, so WebKit now prevents the margins of collapsed blocks from collapsing with parent margins.
Dirk introduced the “clip-path” CSS property into WebKit, which restricts the region of an element that can be painted. Changes landed making this work for both HTML and SVG elements, together with a fix which makes sure that the correct origin of polygons will be applied.
![[1]](https://slachtoffer.com/wordpress/wp-content/uploads/2012/11/self-contained.jpg){kind=link}
