Another 1,492 commits have been added to the projects; 826 to Chromium and an evil 666 to WebKit. Highlights include support for <ol reversed>, lots of changes for CSS Filters and rendering CSS Shaders.
Going forth in improving security in the browser, Chromium will now display a fatal error when it encounters pages using SSL certificates signed with the MD2 and MD4 hashing algorithms, and will display an interstitial warning page for certificates signed with MD5. Certificates with RSA and DSA keys of less than 1024 keys will also be rejected.
Within Web Inspector, a sidebar has been added to the Script Panel displaying the included scripts on by their host. A large amount of internal properties of objects using the Detailed Heap Snapshot tool have been hidden and hex-colors with just three characters will now be highlighted.
A significant memory improvement for Windows, sometimes yielding 5% improvement.
Another 4% speed-up on Kraken for Apple’s new DFG JIT.
Visited link hashes will now be cached, speeding up the total CPU usage on the HTML5 spec by 1%.
Since next Monday happens to be Boxing Day, I’ll publish a (probably brief) update the day after, Tuesday the 27th. Thank you for reading and have a Merry Christmas!
With 912 commits at Chromium and 590 at WebKit, totaling up at 1,502 changes, a fair amount of changes have happened again. Highlights include Mutation Observers for Chromium and animatable background images.
Chromium has reached a version number which equals a pentagonal pyramidal number: 18. In total, 7,107 Chromium commits, 4,198 WebKit commits and 526 v8 commits are included, totaling up to 11,831 changes for the Google Chrome 17 release, besides changes in other related projects such as Skia and NaCL.
Mutation Observers have been enabled for Chromium, which provide a much better alternative to DOM Mutation Events. Though still disabled by default, Chromium has been taught how to handle meta viewport elements, the scoped attribute for scoped stylesheets landed, table cells now understand widths in percentages and security around loading out-of-band text tracks has been improved by utilizing CORS.
WebKit now supports animations between background, border and list images utilizing the cross-fade() function which landed a few weeks ago. Parsing for multiple grid rows and columns has been added, as has parsing for the wrap and wrap-reverse values for the flex-flow property.
As a first step in being able to CSS Regions, background colors will now be applied. The behavior of !important in inline style sets has been aligned with the specification, automatic color adjustments for disabled input elements has been removed for Chromium and variousmore CSS 2.1 test failures have been fixed.
Other changes which occurred last week:
The Screen, Terminal and VT100 classes, all part of an HTML-based terminal emulator, landed.
A shutdown option has been added to Chromium OS’ wrench menu.
Chromium Profile avatars will now be displayed in Windows profile-specific shortcuts.
And that’ll be all for last week again. Things to keep an eye out for this week include custom written CSS Lexer and work by Simon Fraser to make the CSS Filter property animatable!
Following the relatively low count of 1,097 changes two weeks ago, last week introduced a combined total of 1,945 changes, 1,186 at Chromium and 759 at WebKit. While many of these changes were part of the rush for features to make it into Google Chrome 17 (which will be branched tomorrow), highlights include two important new features for the Flexbox implementation and a Socket API.
A few updates have been made to Chromium’s extension APIs, namely that the MHTML and webRequest APIs have been moved out of the experimental namespace, and a checkpointcommit for a new Socket API. While it’s not functional yet, it will eventually allow for extensions such as SSH and IRC clients to be made.
The visual appearance of Panels has been worked on quite a lot last week, with a visual refresh landing on Chromium for Mac OS X, together with a three-stage minimize animation. For Windows, the UI has been updated as well, and Panels can now also be drawn in iconified mode.
As for specification support, WebKit’s implementation of the bdo, bdi and output elements is now mostly aligned with the HTML5 specification. Limited parsing for the grid-columns and grid-rows properties has been implemented, CSS Filters will now render correctly on transformed elements and CSS Flexbox has been taught about reverse rows and columns. Images’ sources can be overwritten using the CSS content property now, and the correct focus rings for areas defined in an image’s image map will now be shown for zoomed pages.
Thanksgiving made last week a short week for people living in the United States, and as such only 1,079 changes landed to the Chromium and WebKit repositories. Highlights include a number of extension API updates, work on supporting game controllers and WebGL for the WebKitGTK port.
In light of the recent commit milestones Chromium and WebKit hit, it’s noteworthy to add that v8 reached revision 10,000 last week. Performance of switches using string clauses has been improved and preliminary detection for ES.next’s extended mode has been added, which basically reflects strict mode with some added functionality.
Chromium’s embedding code for GetUserMedia has been implemented in WebKit, another step closer.
The WebKit-side of supporting asynchronous spell-checking landed last week.
Usability of Web Inspector’s auto-complete suggestion box has been improved.
Some test-cases have been added for the Pointer Lock API at WebKit.
And that’s it again. Interesting changes for the upcoming week include the NamedFlow JavaScript interface for CSS Regions and stack traces for cross-origin access errors within Web Inspector.
Last week was the busiest week so far for both projects, totaling up to 1,745 changes — 794 for WebKit, and 951 for Chromium. Highlights include CSS Cross Fading, Flexible Box, Filters and <meta name=referrer>.
Within Chromium, the new History UI has been launched and can be seen on chrome://history. Content Security Policy will be enabled for all extensions using a (newly introduced) manifest version of two or higher and improved download protection has now been enabled by default, assuming you have Safe Browsing enabled.
Timothy Horton landed support for the CSS4 Images cross-fade() function. Though not fully implemented yet, it can be used as a value for any property that expects an image, such as background-image, and will render a cross faded combination of the two given images or gradients. Examples working in nightlies can be found here.
Another new feature which landed today is support for <meta name=”referrer”>. By specifying the referrer policy in the content attribute, which can be one of never (don’t include a referrer header on navigation), always (which includes cross-protocol requests), origin (just send the page’s origin) and default, you can anonymize any request.
With another 1,616 commits down the pipeline, 904 at Chromium’s and 712 as WebKit’s, another very busy week has passed. The highlights include a first working CSS Filter, the hundred-thousandth commit for WebKit and the ability to change your user agent in Web Inspector.
Web Inspector now shows the media queries which are associated with certain CSS Rules. The user agent with which a page gets loaded may now be changed, selected text in a Script panel received an extra context menu option to evaluate it directly in the console and a suggestion box will now be shown for both CSS as JavaScript properties. Finally, the indentation of pretty-printed JavaScript can now be configured.
Dean Jackson added code to WebKit’s CSS Parser, making it understand the syntax for drop shadows. Meanwhile, the first part of parsing the custom() filter definition, used for CSS Filters, landed as well. Support for parsing the line-grid-snap property has been added as well, which will allow snapping of text towards the nearest enclosing grid.
For WebKit ports who have CSS Filters enabled, the hue-rotate() filter started working per Dean’s plumbing of filter effects through the rendering code. Small as it is, it’s enough to be excited about :).
Last week, 1,332 changes landed in both repositories: 768 at Chromium’s and 564 at WebKit. Highlights include the possibility to print background images and colors, a vastly improved GC for Apple’s JavaScriptCore and quite some updates on Content Security Policy following last week’s TPAC.
A multi-threaded accelerated surface implementation has landed now for Chromium on Windows as well, which, together with a follow up patch, will aid in having multiple windows rendering at 60 frames per second.
Following discussion at last week’s TPAC, WebKit’s Content Security Policy implementation has been updated to handle empty URLs, the allow-popups directive has been implemented on request of Microsoft, as has the sandbox directive, which basically mirrors the “sandbox” attribute for html and iframe elements.
In terms of specification compliance, the CSS Parser has been adjusted to accept any character in a string except for newlines and the string-opening quote. Finally, window.onerror will now fire for exceptions and errors in attribute-scripts. Canvas objects can now be exported to WebP images and using a border-box box-sizing with elements that have display on table-cell won’t calculate the content height anymore.
In the past few weeks, a lot of performance improvements already landed for Apple’s JavaScriptCore, followed this week by another 3.8% on Kraken and 3.5% on v8. The latter is especially interesting, as it adds parallel tracing to the garbage collector, reducing GC pauses by almost 50% in day-to-day usage!
A compile time flag has been added for CSS Shaders, indicating that work there will be starting! A fair numberof bugs has already been created, which are being worked on together by Adobe and Apple engineers.
Other changes which occurred last week:
As discussed, Adam Barth started with moving WTF out of JavaScriptCore.
The arithmetic composite SVG Filter has been optimized for CPUs supporting ARM-Neon instructions.
Another 1,511 changes further on, 885 made at Chromium’s repository and 626 at WebKit’s. Last week’s highlights include upstreaming of OpenBSD support into Chromium, lots of progress on implementing support for HTML5 Microdata and first steps towards supporting the CSS cross-fade() function for images.
Within Web Inspector, it’s now possible to select the indentation which will be used in the text editors. The four options available are two, four or eight spaces, or a tab. Advanced search is now available for content scripts and inline background-image CSS properties won’t show a warning anymore in the console.
Arko Saha’s work on implementing the HTML5 Microdata properties and DOM API is progressing nicely, as the itemprop, itemref and itemvalue properties landed last week. The itemtype attribute has been enhanced to accept a space-separated list of values, and code for the itemid attribute is justabout to land as well.
As for specification related improvements, drawing images on a canvas by using certain composition modes has been fixed. Input step-values may now start with dots, IndexedDB has been taught the deleteDatabase method and two patcheslanded implementing parts of the Mutation Observers specification.
Parsing of two new CSS features has landed, namely for line-grid and for the cross-fade() function. The former is a shorthand for line-grid-mode and line-grid-progression defined in the CSS Text Module, whereas the latter allows cross fading images and is defined in CSS Image Values Level 4.
Other changes which occurred last week:
Accessibility of the omnibox in Chromium has been vastly improved.
With 974 changes to Chromium’s repository, and 637 at WebKit’s, last week totaled up at 1,611 commits. Highlights are the new Chromium version, work on the Mouse Locking API and more work on Regions.
Chromium has reached version 17. The number, which also happens to be a repunit prime when written in base-16, supersedes the now branched Chrome 16. There are about 5,500 Chromium revisions going in the 16th major.
Vincent Scheibb has been working on a Mouse Locking API, the back-end for the settings of which landed in Chromium last week. Meanwhile, the WebKit side of the implementation is also starting, with the ability to toggle the feature either at compile or run-time.
As for specification support, the -webkit-from-flow value for the content property has been changed into its own property: -webkit-from-flow. Furthermore, the @-webkit-region at-rule can now be parsed, support for XPath is now enabled for all ports and the new Flexible Box Module implementation can now handle column flows.
Rendering of certain column-rule styles in vertical writing modes has been fixed, the ArrayBuffer object now supports the slice method, IDL files for the <track>-element have been added and content can now be clipped to variable width regions. Column rules will now be positioned correctly in vertical layouts when horizontal borders or paddings apply. Twopatches have been committed in relation to the new Mutation Observers API as well.
Last week introduced another 1,540 changes in the WebKit and Chromium repositories, which beats the previous record of 1,515 commits. Highlights include a branch for the Web Component Model, first steps in WebKit’s Microdata implementation and searching through multiple scripts in Web Inspector.
The Web Component Model has received its own branch at WebKit, allowing initial work to start. The Component Model provides programmatic ways to ways to build components, utilizing features such as the Shadow DOM, templates and the ability to create your own elements. It layers a declarative form of the same capabilities on this infrastructure, making it available to most HTML developers. See Alex Russell’s slides for more information.
A number of updates were done to Chromium’ Extension APIs. The Permission (docs) and Panel (docs) APIs have been moved out of experimental, whereas support for a new experimental Clipboard API has been added, which will grant extensions access to the system’s clipboard. Finally, the onAuthRequired callback in the webRequest API can now provide credentials when needed.
Within Web Inspector, support was added for an advanced search feature in the Scripts Panel that allows you to search through multiple scripts at the same time. Back-end work was done in preparation of supporting the ability to debug shared work initialization, and the ability to look up and explore an object from an heap profile was added.
As for specification support, the first patch for implementing HTML5 Microdata has landed, namely the getItems() method. For CSS Regions support, the content-order CSS property has been removed, flowhas been renamed to flow-into and positioned blocks now work with variable width regions.
Robert Hogan has landed threemorepatches fixing tests from the CSS 2.1 test-suite, the event.layerX and .layerY properties have been removed, the :checked pseudo-element selector now matches a selected option and right-margins will be taken into account for vertical writing modes. Finally, the new CSS3 Flexbox implementation now supports flex-align for cross axis alignment in flex-flow: row containers.
Other changes which occurred last week:
The Web Socket implementation has been updated to hybi-17, another breaking change.
