Another 1,301 patches landed last week, 464 at WebKit’s and the rest at Chromium’s, bringing highlights such as the Fullscreen API in Chromium, colored highlighting for Web Inspector and removed code from the Android port.
Within Web Inspector, an element’s margin, padding and content will now be drawn using different highlighting colors, making it much easier to see why certain content may be out of line. The extension API has been updated with the ability to access page resources, and more progresshasbeenmade in the effort to support compiling the front-end using Closure Compiler.
As for progress on the updated Flexible Box implementation in WebKit, Tony and Ojan landed patches adding support for the flex-align, flex-order and flex-pack CSS properties, switched the default preferred width of the flex() function to 0px per a specification update, handling the margins of child elements and behavior when min-width and max-width are used for flexible elements.
Adam Barth and Steve Block removed, aspromised, theAndroidportfrom WebKit. A build slave for testing WebKit’s Chromium port on the Android OS wasadded as well, but hasn’t been activated yet.
Toggling various privacy-sensitive may soon be done via the experimental Privacy API!
And that’ll be all again! Patches to look out for this week include the ability to receive binary WebSocket messages as Blobs and the addition of CORS support for Server Sent Events!
Last week brought another 1,205 changes; 465 to the WebKit repository, and 740 to Chromium’s. Highlights include a new extension API for downloads and fixed composited canvas filling for certain modes.
Within Chromium, stubs for an experimental download extension API have landed. The proposal aims to enable extension authors to offer features such as downloading all the images on a page, and deals with permissions and security concerns accordingly.
An announcement by the Android Browser team was made on the webkit-dev mailing list today in which they announced their intentions of improving collaboration with the WebKit community. The first two steps will be removing all current Android-specific code from WebKit and contributing a build bot to aid in long-term maintenance.
As for specification related changes, region invalidation and repainting now works properly. Canvas fill and fillRect have been taught how to deal with five more compositing modes, WebSocket’s CloseEvent now contains the code and reason properties and text input events for textboxes which may not contain text will now be ignored. Finally, three new CSS properties for CSS Regions were added and content within a region no longer is scrollable.
Among other areas, Accessibility, Document and Element related code now also switched to using the
abstracted LayoutUnit type for rendering positions. Another step closer to float-based rendering.
Web Inspector’s context menu now works properly when debugging remotely.
Long CSS edits in Web Inspector’s style pane will now be word-wrapped.
More work on implementing the bookmark page on the new New Tab Page has been done.
Plumbing has been done in WebKit to start getting scripted full-screen support to Chromium.
Several fixes have been made to get the Idle extension API working properly again.
A fast-path has been implemented to improve painting performance of tables with overflowing cells.
Multiple profiles on Mac are now enabled by default, and the profile avatar icon won’t show up
anymore unless the user actually has more than one profile.
Several measures have been taken to improve the performance of resizing canvases.
Last week brought another 1,245 accepted changelists in the repositories of Chromium and WebKit. Highlights include a new Settings extension API for Chromium, CSS Regions and Exclusions being enabled by default and a separate i18n project for v8.
Chromium’s new New Tab Page, which has been in the works for several months now, now is the default one for the browser. It contains three pages, most visited, Apps and bookmarks, is touch-friendly and accessible. It looks quite good too. If you really want to go back to the former version, you can use the --new-tab-page-3 command line flag.
The experimental Internationalization API that’s being implemented in v8 has moved to it’s own open-source repository, allowing the work to progress more visibly. The API will expose the possibility to utilize features like localized string matching, number formatting and date and time formatting to web authors.
Benjamin Kalman has landed the first part of the long awaited Settings extension API to Chromium. This API will allow extension authors to specify settings for their extensions, which can then be synchronized across a user’s computers. Just like bookmarks. Early documentation is available on Chrome’s Google Code docs.
Within Web Inspector, the Network Panel won’t show local resources statuses as pending anymore. You can now choose to hide user-agent stylesheets in the style panes, the Resource Panel will now show cookies for the main resource, folders in the Script Panel are now optional and it’s now clearer which properties are non-enumerable when expanding objects. Finally, scripts from different domains won’t appear in the same folder anymore.
As for specification related updates, the width of a numeric input will now depend on the values it accepts. Basic horizontal flexing has been implemented for the new Flexible Box implementation and WebSockets now accept multiple sub-protocols and supports the protocol and binaryType attributes. Tom Zakrajsek made sure that unknown HTML elements now derive from HTMLUnknownElement and advanced text shaping was implemented for Linux.
Following thesetwo commits, Ryosuke Niwa was finally able to claim victory on his crusade to get rid of wrapping spans and Apple’s Apple-style-span class in WebKit’s editing component. His work resulted in much cleaner generated HTML for editable components.
With just 1,227 commits in the past week, 487 at WebKit’s and 740 at Chromium’s, it has been a normal week again. This week’s highlights include a new validation message UI, two full-screen modes for Chromium on Mac OS X Lion and the first step in supporting low level font features through CSS.
With Nico Weber toggling the switch, Google Chrome versions 15 and beyond will no longer use GCC for compiling the source, but instead will be using Clang. Clang is the C, C++ and Objective C front-end for the LLVM compiler. This change has led to a size-drop of well over 10 megabytes in the size of Chromium.app!
In the effort of improving Chrome’s support for Mac OS X Lion, status bubbles will have their corners rounded appropriately now. More importantly, the concept of full-screen has been split into two modes: Lion’s own interpretation of “full-screen”, placing the window in it’s own space while still having a visible dock, and a presentation mode which is a more conventional full-screen mode.
After adding a new performance test for float element lookup, Adobe’s Alexandru Chiculita landed an optimization which yields a performance improvement of about 150% for looking up a floated element. Nice!
As for specification related work, using a percentage value for an object’s border attribute now works appropriately. The PeerConnection interface from the Peer2Peer API has been implemented, a VTT parser has been added for subtitles for the <track> element and an important part in supporting <input type=color> has landed too.
Last week brought 1,352 updates to the projects, 445 for WebKit and 907 towards Chromium’s repository. Highlights include Chromium 15, the download attribute and work on implementing positioned floats.
The Web Intents shim was announced by Paul Kinlan about a month ago, and last week the initial signs of Chrome’s implementation started to show up. While it’s only preparatory work so far, a command line switch has been added and work on WebKit’s side is about to start.
In light of adding a cd()-like feature to Web Inspector, some refactoring has landed last week. An initiator column has been added to the network overview, and instead of disabling it altogether, the cache will now be cleared after navigation. Custom getters in the property pane won’t appear dimmed anymore.
As for specification-related changes, the selectionDirection property on input and textarea elements is now supported, just as the sizes attribute for link-elements is now supported as well. Specifying unicode-bidi as plaintext on textarea elements works correctly again, behavior of the Float32Array constructor has been fixed and v8 can now actually serialize script elements correctly.
Following Darin’s announcement, this response from Ian Hickson and the actual edit to HTML, WebKit now supports the download attribute on anchor elements. It’s quite simple really: specify the download attribute, optionally defining a filename, and the browser will download the anchor’s location rather than navigate to it.
Dave Hyatt has started to work on implementing positioned floats in WebKit. Currently, floated elements either float to the right or left side of their container, allowing content appear on the opposite side. Positioned floats allow floated elements to appear, for example, in the middle, spreading content between the left and right hand area’s of the floated element. While there definitely is progress, no actual rendering effects will be visible at this point.
Other changes which occurred last week:
The first basic layout test for the Web Audio API landed!
A remarkable change from Apple’s side: support for a built-in -webkit-pictograph font which can
render image-like glyphs. The font face itself seems to be private.
Chrome can now identify itself with the freeway running between California and Montana.
Larger hit-boxes will apply to select-boxes when Touch UI support has been enabled.
Knobs of disabled range controls will no longer be draggable.
The Data-tab of Chromium’s net-internals page has been split up in three tabs: Import, Export and Capture.
Tests for validating WebKit’s WebVTT parser (for <track>) have been added.
Printing an accelerated canvas in Chromium now works properly again.
As work on WebKit’s brand new XML Parser continues, a wild tokenizer appeared.
Chromium’s close-animation on Mac OS X has been sped up by request of the Gods.
The avatars available for multiple profiles have been revised, and several new ones have been added as well.
Chromium will now remember whether you wanted to print the last page in grey-scale or in color.
The filename-text for file upload controls is now properly aligned with the button-text for various platforms.
Splitting up the chrome-library in components can now create views.dll/.so as well.
Work on eliminating 2-pass painting for composited pages already gained 20% in performance in tests.
Support for bitmap images was added to Chromium OS’ file browser.
Two new experiments related to Instant will be done with 10% of the Google Chrome users.
The Web UI Task Manager will be enabled by default for the Chrome OS 14 release.
Motorola is busy adjusting WebKit GTK to use the v8 JavaScript engine.
And for a pretty exciting update on browser usage: open source-based browsers (being Chrome and Firefox) now serve the majority of the web with a combined market share of 50.09%! That is pretty cool.
Another 490 commits landed in WebKit’s repository last week, together with a massive 938 commits to Chromium’s, totaling up to 1,428 changesets. This week’s highlights include the ability to completely disable cache in Web Inspector, per-user proxies and quite some changes to Chromium.
Whereas using proxies on Chromium OS used to be system-wide, thus shared among all users and networks, Kuan Tan has added support for more flexible per-user and per-network proxies. Especially for those using corporate networks, as well as personal ones, this is a very welcome enhancement.
Another notable addition is that active audio streams will now be displayed on the chrome://media-internals/ page. So if you’re one of these people with hundreds of tabs open when one of them starts making noise, now you know where to find which tab to close.
As for specification related updates, using the “none” value when using multiple backgrounds will no longer break other images. Calculating the height of replaced elements has been fixed according to CSS 2.1 content height rules, support for HyBi WebSocket Frames has been added and the microphone icon for right-to-left input elements will now be positioned correctly, just like numeric input types have also been fixed for rtl.
v8’s implementation of serializing script values has been brought up to speed with the specification, a Ping-From header will now be included for cross-origin, non-secured connections when clicking <a ping> anchors, three new SVG elements won’t collapse anymore when paginating content.
Other changes which occurred last week:
Focus and selection events will now fire when the selected value of an <select>-element changes.
Naming has been clarified for registerProtocolHandler’s messages on the mailto: and webcal: protocols.
The dimensions of buttons on the virtual keyboard will now be determined through CSS Flexbox.
An early collection of multiple-profile avatars has been added to Chromium.
As part of progress on implementing the Peer Connection API, an AudioInputDeviceManager has been added.
Thousand separators for numeric input types have been disabled, as they’re not always convenient to have.
Apple has enabled the DFG-JIT for x86-64 Mac OS X platforms!
And that’ll be all for this week again. Things to watch out for this week will be work on CSS Flexbox and Regions, as well as more media related commits.
Last week brought 1,204 changes to the Chromium and WebKit repositories, with highlights such as work on the new Web Sockets protocol, a minimum window size on Windows and collectively improving Web Inspector.
Web Inspector is now able to show alert modal-dialogs in docked mode as well. More work has been done on enabling debugging of Shared Web Workers, performance of panel switching has been improved, resizing of the sidebar pane has been fixed for the Timeline and Profile panels and a flickering “please wait” message on Chromium has been removed. For Chromium, some infrastructure has been added for optionally gathering user metrics, which in the long run can be used to improve Web Inspector based on actual usage. Finally, welcome to John J. Barton!
As for improved specification support, Chromium on Windows is now able to hide the cursor by setting cursor: none. Canvas compositing with a global destination-atop now works properly, SVG Text rendered by Chromium will now always use geometricPrecision, associating form elements with non-existing forms has been aligned with the ES5 specification. Finally, in order to improve coverage of tests over the CSS Selectors implementation, the official test-suite has been imported.
Work on implementing the latest Web Socket Protocol is coming together nicely as well, tools are being updated, the new hand-shake has been implemented and a patch for the updated framing structure landed earlier today. Adobe added parsing of two new properties as well, CSS Region’s content-order property and Exclusion’s wrap-shape one.
Other changes which occurred last week:
A WebRTC Audio Device has been implemented for the renderer process, start of binding it with WebKit?
Accessibility notifications have been added to the range input-type when its value changes.
The new New Tab Page now includes a link to the Chrome Web Store, which cannot be uninstalled.
Improvements for Chromium’s component build: a separate UI library and one define instead of many.
An experimental implementation for SPDY over WebSockets has been added to Chromium.
Initial support for remote Cloud Print servers in the Print Preview dialog has been implemented.
Much later than usual, but live from Mountain View this time! Last week brought 838 updates, 468 at Chromium’s, the rest at WebKit’s. Highlights include work on a new tool for WebKit Gardeners, many updates for Web Inspector and two more parsing patches for Adobe’s CSS Regions.
Adam Barth started to work on a new Gardening tool for WebKit, called garden-o-matic. Gardening is the act of making sure that the build tree remains green, ensuring there are no unexpected test failures, etcetera. The idea is to provide a dashboard to developers allowing convenient access to actions like reverting changes, finding unexpected failures and the build which made them fail.
Now that WebRTC has landed as a Chrome dependency and work on implementing several related features in WebKit is well on its way, Magnus Flodman landed an early implementation of the Media Stream Manager. This Manager will coordinate between WebKit’s API, permissions, WebRTC and of course your camera and microphone, ensuring that the feature will work smooth and secure.
The multiple profile feature has received quite some work as well this week. The setup UI for a new profile has been implemented, deleting profiles now is a possibility, the displayed avatar can be customized and will contain most profile-related options. Finally, it has been enabled by default on the Views UI, presumably Chromium OS.
An incredible amount of changes happened for Web Inspector last week. You can now drag and drop elements and other nodes in the Element Pane, a new settings panel hasbeen added, and cache and cookies can soon be removed via the Network Panel. Speaking of which, you can now also search in the Network Panel, albeit still limited to filenames and paths.
The specificity of !important properties for the Inspector has been fixed, links to stylesheets will now open in the Style Panel, multiple resources will be shown when a URL is referred to multiple times and requests made by plugins will be shown in the Network Panel. Finally, it’s now clearer how to add a new style rule and adding CSS properties will no longer result in messy CSS rules.
As for specification related updates, the value property of an indeterminate progress bar will now return zero. A change event will be triggered when the selected files of a file input change, column-break-inside: avoid has been re-enabled and more key-bindings have been added to range inputs. Furthermore, parsing capabilities for the flow and from-flow properties, as part of their CSS Regions proposal. Finally, more workonswitching WebKit’s Render Tree to a float-based representation hasbeendone.
Other changes which occurred last week:
A new user interface for the media controls in Chromium is being implemented, though not yet available.
Shaders will now be shared among multiple compositors, improving performance as compiling them is expensive.
Audio rendering can now be done through a low-latency path, eliminating several noticeable delays.
Flicker when switching tabs on Chromium OS has been fixed.
The text-to-speech extension API has been extended with additional info, such as word boundaries.
The login keyboard for Chromium OS now uses an animation to slide in, rather than pop-in.
Support for ShadowBlur was added to the Qt port, improving performance.
Zoltan Herczeg now is a WebKit Reviewer, congratulations!
And that’ll be all! I will be in the Mountain View area until July 23rd and will attend Open Web Camp III (thanks, John Foliot!). If you want to meet up, feel free to drop me a note.
Last week brought 1,367 changes to the projects, 572 for WebKit’s repository and 795 for Chromium’s. Highlights include Samsung’s WebCL prototype, an experiment which disabled modal dialogs in the onunload event and the recent steps to move away from an integer-based render tree.
Samsung has announced the direct availability of a WebCL implementation for WebKit. While the prototype is limited to newer Apple laptops running Mac OS X, the work by itself looks promising. Nokia did something similar, they created a WebCL extension for Firefox.
Just over a week ago, Sreeram Ramachandran posted a message to the webkit-dev mailing list with statistics about websites using modal dialogs in the onunload-event: 2.3% of all users encounter at least one such modal dialog every week. Despite mixed opinions on the list, Chromium will no longer allow modal dialogs (such as those spawned by confirm() and alert()) in this event.
A few interesting changes have been made for Web Inspector. The boundaries of grouped console messages have been clarified, and nested groups won’t be merged anymore. Preparations have been made to allow pseudo-class style inspection in the future and various new entries have been added in the HAR output for requests. Finally, node selection has been sped up significantly.
Quitesomework has been done in the effort to move away from using integers for Layout in WebKit. The main rationale behind moving towards a float-based rendering tree was to allow for better zooming and scaling support, but in the long run this may lead to support sub-pixel layout and positioning. WebKit is the only engine which doesn’t support this internally yet.
As for standards support, WebKit now handles adjacent sibling-selectors with the <nav>-element correctly. Multiple e-mail addresses may now be separated by spaces, the legacy color-attribute parser has been updated to match the HTML5 specification (by Tab!) and the autocomplete DOM property for forms is functional again. Support for the plaintext value for the unicode-bidi CSS property has been added as well.
It’s been a while, and even though I cannot guarantee the updates to become weekly again, here are the highlights of last week’s 1,366 commits. They include a rollout of the SpellCheck API, early work on smooth scrolling for Chromium and a decreased maximum depth of the created DOM tree, namely 2048 levels.
Even though it won’t be functional yet, since last Tuesday it is a possibility to enable the Media Stream APIs in WebKit by passing the “--enable-media-stream” command-line flag to Chromium. Furthermore, following some fine-tuning and a commit saying that the basic implementation of Remoting hosts has been completed, work in the Remoting feature seems to progress steadily.
Following this announcement, WebRTC has now become a dependency of Chromium. Inclusion of the library in the browser will definitely aid in work bringing camera and microphone access to web applications, as well as the ability to stream that -and other- information to other users.
Two interesting Web Inspector changes are the addition of a context menu item for enabling inspecting native workers in Chromium, and the ability to pause the debugger on changes to an element’s style attribute.
As for on-going work, Tony Chang and Ojan Vafai have announced to start working on adding support for the new CSS Flexbox specification to WebKit, the first patch of which landed last Wednesday. Yuta Kitamura announced to start implementing the latest WebSocket protocol (-09), the first patch of which landed as well. According to Ian Fette, the protocol is mostly finished. Both features are still disabled by default.
