CSS parsing errors, JavaScriptCore updates and font load events

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

1,226 Chromium changes and 717 WebKit changes add up to a total of 1,943 changes last week.

Work has started enabling Web Inspector to report various CSS parsing errors, such as mismatched braces and missing semicolons. A menu has been added allowing you to customize the panels displayed in the toolbar, capitalization of menu items has been made consistent and IndexedDB data may now be cleared.

WebKit’s Content Security Implementation will now fire a “securitypolicyviolation” event whenever violations occur, and will include the effective-directive key in violation reports as well.

Intrinsic sizing (i.e. min-content) now work on flexible box elements, and parsing for the -webkit-each-line value for CSS 3’s text-indent property got implemented as well. The Grid Layout implementation now supports default grid item sizing, and can parse the grid-auto-{column, row} CSS properties.

Apple’s JavaScript engine ninja Filip Pizlo filed a series of bugs covering some future plans and experiments in regards to JavaScriptCore. Ideas including changing it to a quadruple-tier virtual machine, allowing it to do more optimizations for longer running scripts, running the optimizer on awesome new threads and experimenting with LLVM as a backend.

Other changes which occurred last week:

I unfortunately won’t be able to share an update next week. Be sure to check out Šime Vidas Web Platform dailies instead!

2 Responses to “CSS parsing errors, JavaScriptCore updates and font load events”

Both comments and pings are currently closed.

Achshar

March 29, 2013 at 8:19 am

Any idea when speech synthesis be available? Not to chrome extensions via chrome.* api but to regular web apps.


Randall

April 3, 2013 at 11:49 pm

Ah, wow–should I expect Blink updates now?