But both changes are interesting, so I’ll explain them here.įirst is a change in AppleScript.
#Leopard webkit mac os x
I’ve updated the code in the original entry so that everything now works both in Snow Leopard and in Mac OS X 10.5.
#Leopard webkit how to
Snow Leopard, which Apple has said will ship sometime next year, will focus on stability and performance improvements, rather than on adding more features to the operating system.Snow Leopard Compatibility Tweaks for That Thing I Wrote in January About Writing AppleScripts That Dynamically Target Either Safari or WebKit Monday, 14 September 2009īack in January I posted this piece about how to write AppleScripts that dynamically target either Safari or WebKit, depending on which one is your default (or which one is currently the active app). Mozilla plans to add TraceMonkey to the next edition, Firefox 3.1, due to ship sometime later this year or in early 2009.Īccording to reports, Apple will integrate new builds of WebKit into its Safari 4, which has been seeded to some developers for testing and is expected to publicly launch with Mac OS X 10.6, aka "Snow Leopard," the next version of the company's operating system. last month, when the company spelled out massive speed gains from its TraceMonkey project. Stachowiak's comments followed similar claims by Mozilla Corp. In related news, Stachowiak also recently revealed that a major revamp in WebKit's JavaScript engine, dubbed "SquirrelFish Extreme," was more than twice as fast as its predecessor, and over three times faster than the engine included in the current production edition of Safari. The only other browser maker to stake a claim on Acid3 has been Opera, which said six months ago that a development build of its flagship application had also scored 100.
#Leopard webkit windows
In the Windows XP SP3 virtual machine, all production and preview versions - the latter indicated by build numbers or status in parenthesis - scored less than 90 on the test. However, when the most recent Mac OS X WebKit, build r37012, was tested on the same machine, it scored 100 and finished each test under the 0.33ms mark, confirming Stachowiak's claim.Ĭomputerworld 's tests also confirmed his statement that no other major browser could match WebKit's Acid3 score. Although WebKit scored a perfect 100, it could not complete all tests in the required time in the virtual machine one test repeatedly failed to meet the 0.33 millisecond cut-off. Google's browser, however, relies on a version of WebKit older than the one touted by Stachowiak.Ĭomputerworld tested the newest WebKit, build r36882, in a virtual machine running Windows XP SP3 on an iMac powered by an Intel 2.4GHz Core 2 Duo processor. WebKit provides the core engine for not only Safari, but since early this month, also Google's Chrome. When a browser finishes each test in that time or less, Acid3 shows the message "No JS errors and no timing issues" in a pop-up window. Last Thursday, however, Stachowiak said that the newest builds also met Acid3's "smooth animation" requirement, something it had failed to do in March, by completing each test in under. The test, which was approved last March by the Web Standards Project, is designed to check how closely a browser follows certain standards, particularly specifications for Web 2.0 applications, as well as standards related to the DOM (Document Object Model), CSS2 (Cascading Style Sheets), and SVG (Scalable Vector Graphics). The claim was a follow-up to last March's boast by WebKit developers that the browsing engine had scored 100 out of a possible 100 in the Acid3 test. "WebKit is the first browser engine to fully pass Acid3," said developer Maciej Stachowiak in a post to the WebKit blog. Developers working on WebKit announced late last week that the newest build of the browser engine, which powers both Apple 's Safari and Google 's Chrome, has aced all of the requirements of an important Web standards test.
0 kommentar(er)
