WebKit builds have been > 14 MB starting with r27031 on 2007-10-25, when Leopard (in addition to Tiger) was included.
Why would a browser engine would need more code to work with a new OS? Would that be the work of Safari, not WebKit? I recall using WebKit nightly builds prior to the official release of Leopard.
Why would a browser engine would need more code to work with a new OS? Would that be the work of Safari, not WebKit? I recall using WebKit nightly builds prior to the official release of Leopard.
Because nightlies starting from that day ship for both Tiger and Safari. There are two (slightly) different versions of the frameworks in them.
Not more code, just the same code compiled with different dependencies and optimizations.
Comments
You won't have to punch the monkey because iPhone has the best adblocker ever, no Flash support.
Most ads aren't flash.
Most ads aren't flash.
o rly
There are some plain HTML ads but those ads are much less annoying and CPU-hungry than the Flash ads.
But even this plain 'Wacom' ad that I'm looking at right now with no animation is Flash. Can you imagine?
WebKit builds have been > 14 MB starting with r27031 on 2007-10-25, when Leopard (in addition to Tiger) was included.
Why would a browser engine would need more code to work with a new OS? Would that be the work of Safari, not WebKit? I recall using WebKit nightly builds prior to the official release of Leopard.
Why would a browser engine would need more code to work with a new OS? Would that be the work of Safari, not WebKit? I recall using WebKit nightly builds prior to the official release of Leopard.
Because nightlies starting from that day ship for both Tiger and Safari. There are two (slightly) different versions of the frameworks in them.
Not more code, just the same code compiled with different dependencies and optimizations.