Blogs›Google›Blink Rendering Engine
The Blink rendering engine was introduced as a fork of WebKit, aiming to provide a more efficient and flexible foundation for the Chromium project. This marked a significant architectural shift in how web content is rendered within Chrome and other Chromium-based browsers, focusing on performance and developer control. Google Chrome Frame was introduced to bring modern web technologies like HTML5 and CSS3 to older versions of Internet Explorer, allowing developers to leverage these advancements. HTML5 and WebKit are now paving the way for mobile web applications, enabling richer and more interactive experiences on mobile devices.
4/3/2013
This post announces the creation of Blink, a new rendering engine for the Chromium project, forked from WebKit. It highlights the goals of Blink to improve performance, efficiency, and flexibility in rendering web content, and its role in the future development of Chrome.
11/30/2009
This post announces new functionality for Google Chrome's Developer Tools, including a new JavaScript debugger, a DOM inspector, and a timeline profiler for analyzing performance. These additions aim to provide developers with more powerful tools for debugging and inspecting web pages.
9/22/2009
Introduced Google Chrome Frame, an open-source ActiveX control that embeds the WebKit rendering engine into Internet Explorer. This allows developers to use modern web technologies like HTML5 and CSS3 on older versions of IE, bridging the gap in web standards support and enabling richer web experiences.
4/7/2009
This post announces that HTML5 and WebKit are enabling the development of mobile web applications. It highlights the potential for richer and more interactive experiences on mobile devices, moving beyond the limitations of older mobile web technologies.
9/2/2008
This post announces the launch of Google Chrome, a new web browser built on the open-source Chromium project. It highlights the V8 JavaScript engine, which provides significant performance improvements for JavaScript execution, and the Blink rendering engine (though Blink was forked from WebKit later, this post marks the initial architectural direction for Chrome's rendering). The post emphasizes Chrome's speed, simplicity, and stability as key design goals.
8/7/2007
This post provides optimization data for HTML5 parser implementors, offering insights into performance characteristics and potential areas for improvement in the parsing of HTML5 documents. It contributes to the ongoing effort to refine the efficiency and accuracy of the rendering engine.