Archive for the ‘Google Chrome’ category (131 posts)

WebGL Inspection, Sticky Positioning and Windows 8 Updates

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 23

Last week saw 993 Chromium commits and 650 WebKit ones, totaling up to 1,643 changes in total.

Chrome binaries will now be signed with compatibility GUIDs for Windows 8, which mainly impacts theming in High Contrast mode and heuristics about potential compatibility issues. Furthermore, forwarding of search queries in Windows 8 UI mode has been implemented, and mouse input events from styli will no longer be ignored.

Web Inspector’s Profile panel is getting a great new (experimental!) feature from Andrey, namely WebGL inspection. The Timeline panel is now able to show the cause for a style recalculation, the console.time() method now uses performance.now() for more accuracy and more work has been done on improving performance.

Simon landed support for sticky CSS positioning, which limits an element to be positioned within both it’s container and the viewport. Support for parsing the -webkit-text-decoration-style has been added, the arguments for the blend-mode property can now be parsed and CSS masking and filters are now being applied in the right order.

Blob and File System URIs are now considered to be same-origin for Content Security Policy and computed styles for 2D Transforms have been aligned with the specification. An initial implementation of CSS Exclusions’ shape-inside property landed, WebKit didn’t miss out on the usual set of Flexbox improvements and David’s work on re-implementing Multiple Columns on top of CSS Regions saw two more commits.

The postMessage() function now accepts any kind of data as its message, allowing you to post arrays and objects as well. Changing the class attribute on any kind of element will now update the classList as well, and work is being done for allowing pointer lock in sandboxed iframes. The automatic DOM transactions feature for Undo Manager is now implemented, just like the item() method, and the undoscope attribute has been removed.

Another new feature which is in the works, is being able to use the “overflow-y” property as a way to make the render view paginated, as part of implementing the Generated Content for Paged Media specification.

Other changes which occurred last week:

To finish with some other nice news, yours truly became a full Chromium committer last week :).

Read more (3 comments) »

Filtering Network Requests, Blend Mode and two more CSP Directives

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 23

Last week, 764 Chromium commits and 615 WebKit commits landed, totaling up to 1,379 changes.

Especially for Web Applications, finding certain files in the Network tab can be difficult, as there can be hundreds. Web Inspector now gained support for filtering the display based on search results! The BlackBerry 10 user-agent can now be selected in the Settings dialog, and work is being done to improve performance by loading panels lazily.

Parsing support for CSS’ blend-mode property, defined in the CSS Compositing and Blending specification, has landed. The volume sliders for fullscreen and normal media elements will now stay in sync, the first call to webkitRequestAnimationFrame won’t return 0 anymore and z-indexes now work on flexible items without explicitly positioning them.

SVG Filters can now be drawn in the correct colorspace for WebKit ports which don’t use CoreGraphics. Mike implemented the plugin-types and form-action Content Security Policy directives, together with their respective DOM APIs, and support for author Shadow DOM is now available for the <meter> element. Finally, many more languages now have their localized quotes available for the <q> element.

Other changes which occurred last week:

  • The third-party storage blocking system now also covers WebSQL databases.
  • A compile time flag was added for the new CSS 3 text decoration properties.
  • Chromium received a new audio render method supporting synchronized input and output.
  • Sticky CSS positioning has been enabled on Apple’s Windows port.
  • DNS Prefetching has been enabled for the BlackBerry WebKit port.
  • Gyuyoung Kim is the latest member of the WebKit Reviewer team, congratulations!
  • Within Chrome OS, the offset for a secondary monitor can now be set.

Various new features are still under development in WebKit, and may be near the horizon: @supports and parts of Generated Content for Paged Media (GCPM).

Read more (1 comment) »

Chromium 23, CodeMirror Editing and a flag for CSS Exclusions

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 23

Last week, 831 commits were added to the Chromium project and 665 to WebKit, totaling up to 1,496 changes.

Jim Carrey is going to be very pleased with this change made by Anthony last week, namely kicking Chromium to Number 23. You can read about many changes made for Chrome 22 in this series of articles.

Web Inspector’s editor can now be replaced with CodeMirror by Jan Keromnes, as an experimental feature. It supports basic editing, search, replace and saving, but much more work is to be done before it’s completely usable. The function scope is now visible in the UI, and support for two CSS Region events has been added to the protocol.

A new “all” value for the -webkit-user-select property can now be parsed and initial support for text-decoration-line landed. Four more bugs in the Flexible Box Module implementation were fixed, namely the lack of support for inline flexingpercentage sizing in quirks mode, percent-based margins and behavior when using box-sizing.

ArrayBufferView objects can now be send through Web Sockets, the indexed getter for Microdata will now return undefined instead of empty strings, classList can now remove classes with uppercase characters and window.URL has been unprefixed. The <progress> element now supports author Shadow DOM. Content Security Policy now is nosier about errors and more work was done on CSS Region’s CSSOM implementation.

In terms of new features, a compile-time flag for CSS Hierarchies has been added, and work is being done on implementing Proximity Events in WebKit.

Other changes which occurred last week:

That’s it again, thanks for reading!

Read more (1 comment) »

Key Bindings for Extensions and Media Streams for the Web Audio API

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 22

A total of 1,599 commits landed last week, 745 for WebKit and 854 for Chromium.

Extensions using script badges will soon be able to use the Command API, allowing them to declare keyboard shortcuts for triggering events on an extension. Browser integration will become a lot richer with this addition!

The classList property moved from HTMLElement to Element, so may now be used with other types of elements as well — for example, SVG elements. Implementation of a MediaStreamAudioSourceNode for the Web Audio API has begun and audio destinations now support local and live audio input. For the CSS Regions implementation, the regionLayoutUpdate event will fire on the NamedFlow object now.

Sliders with a <datalist> attached to them will now have their handle snap to the available options, and an implementation for using <datalist> with color input-fields has been added for Chromium. The webkit prefix has been dropped from the Vibration API implementation as it reached Candidate Recommendation. Overflow will no longer apply to table rows and row-groups, instead, it only applies to block containers, and a bunch of improvements have been made to the Flexible Box implementation as well.

A setting and API has been added to WebKit2 ports, introducing an option to disable third parties from being able to store data. Besides blocking cookies, this will also encapsulate storage APIs such as localStorage.

Other changes which occurred last week:

  • An API has been added for WebKit2 ports introducing an option for blocking third-party storage.
  • Work is being done on re-implementing support for quotes and the <q> element.
  • Web Inspector’s User Agent setting screen has been renamed to Overrides.
  • The Pointer Lock API has been blocked for sandboxed iframes, and the old API has been removed.
  • Support for CSS Filters has been enabled for the BlackBerry port.
  • Chromium’s Mac OS X deployment target has changed to 10.6, deprecating Leopard.
  • Speculative resource pre-fetching has been enabled for 90% of the users using Dev or Canary.

Last week of the Olympics. Especially for those of you in London, enjoy!

Read more (1 comment) »

Content Security Policy API, Flexible Animations and Sticky Positioning

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 22

A total of 1,517 commits landed last week, 692 for WebKit and 825 for Chromium.

Web Inspector’s Settings dialog has received a new experimental option to override the Geolocation results. Experimental support for supporting SASS source-maps has been implemented as well, and drag and drop won’t be started anymore when using right clicks.

CSS Transitions and Animations now work between different types of length units, for example from percentage to pixel-based widths. For the Flexible Box Module implementation, percentage-sizes items will now wrap properly and the “order” property will now influence the painting order as well.

Mike added a JavaScript interface for Content Security Policy, enabling authors to apply feature detection to determine the limitations applied to their content. Initializing TypedArrays based on other TypedArrays has been sped up by 3 to 30 times, the undoscope property is now supported and Microdata’s PropertyNodeList interface has been implemented.

As for new features, a build flag was added announcing work on CSS Blending and Compositing. Simon started working on implementing sticky positioning, starting with the compile-time flag and parsing support. Sticky positioning is useful for elements that should remain visible on the screen regardless of the scrolling position, while also sticking to their containing element.

Other changes which occurred last week:

Revision 123,456 for WebKit also landed, last week!

Read more (1 comment) »

Find & Replace, a Slider’s Tick Marks and Image Orientation

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 22

Last week, WebKit received 621 commits whereas Chromium received 810, totaling up to 1,431. They were made by 373 different authors, and include a change adding search and replace to Web Inspector.

Find and replace functionality for source files has been added to Web Inspector, after less than a day of being experimental. Furthermore, an icon has been added for pausing JavaScript debugging.

The top property on the window object no longer is replaceable. It’s now possible to apply Shadow DOM to image elements, invalid script-nonce directives for Content Security Policy will cause WebKit to block script execution and  the calculation for serializing CSS rgba() functions has been corrected.

Sliders can now have tick marks painted if they have an associated datalist, and behavior of negative values for text-indent has been aligned with CSS 2.1. As for experimental work, a compile time flag and parsing support for the image-orientation CSS property have landed. Initial support for positioning grid items by their row and column index is now available as well, and displaying dialogs will now take the open attribute into account.

Other changes which occurred last week:

That’s it again, thanks for reading.

Read more (3 comments) »

HTML5 Dialog Element and getUserMedia() for Chrome Frame

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 22

Last week brought 1,433 commits to the repositories, 611 for WebKit and 822 for Chromium, made by 357 different authors. Highlights include work on the <dialog> element and removal of the hixie-76 protocol.

Within Web Inspector, the looks of the find bar have been updated, and several other parts of the UI are also receiving refreshments. Furthermore, the tab size now defaults to four spaces.

The CSS 3 blur filter will now work correctly when it’s applied to the parent of a fixed position element, and support for min-height and min-width in the CSS Flexible Box Module has been implemented, including the implied minimum size of flex items. The state of state-less form controls, such as password fields, won’t be stored anymore. Date and time input types are now supported by the BlackBerry port as well.

Backwards iteration over HTML Collections no longer has O(n2) performance, making it significantly faster. For CSS Regions, the firstEmptyRegionIndex attribute has been implemented for Named Flows and the getRegionsByContentNode method had “Node” dropped from its name.

A compile time flag has landed, marking the beginnings of an implementation of the HTML5 <dialog> element. Meanwhile, support for the old hixie-76 Web Socket protocol has been removed.

Other changes which occurred last week:

Thanks for reading!

Read more (2 comments) »

Scroll into View, XHR with ArrayBufferViews and Text Autosizing

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 22

With just 770 commits last week, 333 at Chromium and 437 at WebKit, the impact of the Independence Day celebrations is quite visible. Since the open-sourcing of Chromium in 2008, there have been only 11 weeks during which WebKit received more commits than Chromium.

The context menu for nodes in Web Inspector now includes a “Scroll into view” item. Snippets can be evaluated and the visual appearance of Web Socket frames has been improved.

Following I/O’s Chrome for iOS announcement, first steps are being made towards upstreaming the iOS code.

XMLHttpRequest’s send() method is now able to transmit ArrayBufferViews, the “script-nonce” directive from the Content Security Policy specification has been implemented, and a basic framework for Text Autosizing had landed.

BlackBerry enabled support for the Microdata API and scoped stylesheets on their port. EFL also enabled some features, namely support for both the Gamepad and the Microdata APIs.

Read more (4 comments) »

Color Profiles, the DPPX, DPI and DPCM units and CSS Variables

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 21

A total of 1,814 commits landed in the projects last week, 625 for WebKit and 1,189 for Chromium.

Web Inspector switched to using Chas Emerick’s jsdifflib for creating diffs between revisions. A dock-to-right icon has been added to the status bar, the settings screen has been rearranged and the list of local modifications may now be cleared. Furthermore, removing a result in the Profiles Panel can now be done through a context menu, and JavaScriptCore now supports breaking from native callbacks.

Following Chromium for Mac, Tony made sure that the Windows and Linux versions now also support color profiles in images, by utilizing ICCJPEG and QCMS libraries.

Animations and transitions may now be applied to :first-element pseudo-elements. The accept attribute of input elements now accepts file extensions and accuracy of state tracking in radio button groups has been improved. David Barr is making good progress on implementing CSS’ image-resolution property, also adding support for the dppx, dpi and dpcm units.

The Blob.slice method has lost its prefix. The document.documentURI property is now read-only, the overset property of Named Flows will return true when no region chain has been attached and the Pointer Lock implementation was updated with the pointerLockElement property, and the requestPointerLock and exitPointerLock methods.

Luke landed the initial implementation of CSS Variables in WebKit. While it’s disabled by default and not enabled on any platform yet, it’s very exciting that work is on its way.

Other changes which occurred last week:

There will only be a brief update next week, while there won’t be any at all the week after.

Read more (23 comments) »

Unregistering protocol handlers and improved input accuracy

Published on in Google Chrome, Last Week, tech, WebKit.

Last week, Chromium counted 1,018 changes while WebKit received 587.

Web Inspector’s pretty print feature now respects the indenting preferences. Only the root domain will be expanded in the Sources and Scripts Panels and links will be opened by default in the Sources panel, falling back to either the Resources or Network panels.

Nico landed yet another piece in improving Chrome’s experience on Mac High DPI modes, this time initial support for High DPI in web content display. The Chrome Blog has a nice image showing the impact his work has.

Zero is now a recognized number again for numeric input fields. Rendering nested flexible box objects has been fixed, the “order” property now accepts a number rather than an integer and more CSS 2.1 issues have been fixed.

Besides registering protocol handlers, they can now be checked for existence and unregistered as well. The imageSmoothingEnabled setting for 2D Canvas contexts will now apply to patterns as well, client rectangles for frames in scaled pages will return the right values and the Pointer Lock implementation gained support for the change and error events. Finally, a build flag for the Undo Manager has landed.

The Blob constructor now accepts ArrayBufferView instead of a normal ArrayBuffer for its constructor’s parameter. Elements with an empty string as it’s “itemprop” value won’t be listed in Microdata’s properties list anymore and several SVG features now report to be supported through DOMImplementation.

After some more intermediary steps, Yoshifumi Inoue introduced the new Decimal type for an input’s value properties, fixing rounding errors in number and range input fields.

Other changes which occurred last week:

  • Duplicated Content Security Policy directives will now display errors in the console.
  • The “target-DensityDPI” viewport meta value will no longer be recognized by WebKit.
  • Wins of 3% on Kraken and 3% on v8 for the JavaScriptCore engine.
  • Render Nodes lost 8 bytes of weight, saving up to 2.6 megabytes when viewing the HTML5 specification.
  • GPU accelerated canvas can now be disabled through about:flags.
  • Support for DTLS-SRTP (RFC 5764) has been implemented in Chrome’s NSS.

I’m not sure about the schedule of updates in the next few weeks, as I’ll be traveling through the United States. I’ll try to keep up!

Read more (2 comments) »