We want to explore if it is worth maintaining SVG DOM. Can we remove SVG DOM is there something that we need to keep around? If the experiment completely fails, we unroll the changes and know how the SVG WG should proceed with SVG2.
Created attachment 237767 [details] Patch
Created attachment 237769 [details] Patch
Comment on attachment 237769 [details] Patch Attachment 237769 [details] did not pass mac-ews (mac): Output: http://webkit-queues.appspot.com/results/5437169531355136 New failing tests: http/tests/misc/acid3.html http/tests/xmlhttprequest/xmlhttprequest-image-not-loaded-svg.svg
Created attachment 237779 [details] Archive of layout-test-results from webkit-ews-01 for mac-mountainlion The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: webkit-ews-01 Port: mac-mountainlion Platform: Mac OS X 10.8.5
Comment on attachment 237769 [details] Patch Attachment 237769 [details] did not pass mac-ews (mac): Output: http://webkit-queues.appspot.com/results/4660079487877120 New failing tests: http/tests/misc/acid3.html http/tests/xmlhttprequest/xmlhttprequest-image-not-loaded-svg.svg
Created attachment 237780 [details] Archive of layout-test-results from webkit-ews-06 for mac-mountainlion The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: webkit-ews-06 Port: mac-mountainlion Platform: Mac OS X 10.8.5
Comment on attachment 237769 [details] Patch Attachment 237769 [details] did not pass mac-ews (mac): Output: http://webkit-queues.appspot.com/results/6549517742637056 New failing tests: http/tests/misc/acid3.html http/tests/xmlhttprequest/xmlhttprequest-image-not-loaded-svg.svg
Created attachment 237785 [details] Archive of layout-test-results from webkit-ews-03 for mac-mountainlion The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: webkit-ews-03 Port: mac-mountainlion Platform: Mac OS X 10.8.5
Created attachment 237788 [details] Patch
(In reply to comment #9) > Created an attachment (id=237788) [details] > Patch ACID3 will be broken since it checks for SVGRectElement support by asserting rect.width, which this patch removes. A bad check anyway IMO but probably reasonable at the time.
This sounds like something that many people on webkit-dev would love to be notified about. Could you please send an e-mail?
(In reply to comment #0) > We want to explore if it is worth maintaining SVG DOM. Can we remove SVG DOM is there something that we need to keep around? If the experiment completely fails, we unroll the changes and know how the SVG WG should proceed with SVG2. Who is the we here? What data do you plan on collecting to confirm/reject your hypothesis?
Comment on attachment 237788 [details] Patch Hi, Apologies that your patch was not reviewed in a timely manner. Since it's now quite old, I am removing it from the review request queue. Please consider rebasing it on trunk and resubmitting. To increase the chances of getting a review, consider using 'Tools/Scripts/webkit-patch upload --suggest-reviewers' to CC reviewers who might be interested in this bug.