Safari on OS X and iOS is soon to get a helluv alot faster, more scalable and a smaller footprint
http://trac.webkit.org/changeset/164131
Timestamp:
02/14/2014 01:29:02 PM (6 days ago)
Author:
akling@apple.com
Message:
Purge remaining ENABLE(SHADOW_DOM) cruft.
<?https://webkit.org/b/128827>
Source/WebCore:
Remove the remaining 8.8 million lines of Shadow DOM code to align
with goals for intent to ship 60fps on mobile in 2014.
Reviewed by Antti Koivisto.
Tools:
Reviewed by Antti Koivisto.
- DumpRenderTree/gtk/DumpRenderTree.cpp:
(resetDefaultsToConsistentValues):
- Scripts/webkitperl/FeatureList.pm:
- WebKitTestRunner/InjectedBundle/InjectedBundle.cpp:
(WTR::InjectedBundle::beginTesting):
I'm so damn glad they are doing this.
Shadow DOM: http://www.w3.org/TR/2012/WD-shadow-dom-20120522/
Moving it to a modules implementation where it doesn't compromise page size and performance is finally being addressed. They state it's costing 5% of overall page load time just to manage these sub trees.
Mobile hitting 60fps is just added sauce of performance on the desktop/laptop space.
Both Chrome and Safari branches of their respective WebKits are dealing with it, but I definitely prefer Apple's solution.
Comments
akling@apple.com
soon to become
akling@home
soon to become
akling@home
Is Apple that protective of its changes to WebKit itself?
Don't know, simply my attempt at tongue in cheek humour. And yes, I don't think they'd mind their employees posting stuff like this.