With Google concentrating on its own Blink, Apple is tightening the WebKit browser engine code base. That'll limit other projects seeking to customize the browser.
The Norwegian software company plans to throw its weight behind the browser engine used by Google and Apple this year instead of developing its own.
Both Chrome and Safari will move faster when uncoupled from each other, Google argues. But it's not just about technology: Social issues also factored into the schism.
Dave Methvin, a leader of the influential jQuery programming tool, says WebKit is plagued with old bugs. He's not optimistic Opera will help improve the browser situation.
The problem with some Web sites showing block-A characters instead of text in Safari 5.1 is likely rooted in the sandboxing technology in the latest WebKit update. Here are some methods for addressing the issue.
Shepherded by Google, the CSS Regions technology that Adobe hopes will improve Web layout has found a home in the WebKit browser engine.
Google, RIM, and HP now use the WebKit-based browser software underlying Safari. Perhaps that heightened interest is why Apple wants the trademark.
The WebKit2 interface is designed to give Apple's Web browser a better capability to juggle multiple computing processes. Also: the first Firefox 3.6.4 beta.
Two WebKit fixes.
Apple's WebKit development team announced Thursday that the WebKit2 framework will begin rolling out.