3273 2005-06-04 20:26:42 -0700 XSL Transformations should occur on a separate thread 2010-09-15 08:52:07 -0700 1 1 1 Unclassified WebKit XML 412 All All RESOLVED WONTFIX P2 Normal --- 1 hyatt webkit-unassigned abarth ap ian mail webdev oldest_to_newest 10733 0 hyatt 2005-06-04 20:26:42 -0700 XSL Transformations currently occur on the UI thread. This means that a long transformation could end up beachballing Safari (or another Web Kit application that uses it). The transformation should take place on a separate thread and call back to the UI thread once complete to avoid blocking the UI. 26785 1 eric 2005-12-27 13:29:39 -0800 Assigning bugs which hyatt is not actively working on to "nobody" for clarity/consistancy. 100148 2 alex 2008-11-24 21:11:22 -0800 Just to update this old ticket: seems to be still valid for the current version. I've duplicated some part of the code within the following example in order to create a 10 MB file: http://www.w3.org/2001/05/xslt-example/REC-xml-20001006.xml In contrast to a 10 MB HTML file Safari is "beachballing" while rendering/transforming the page. 279440 3 abarth 2010-09-15 00:47:38 -0700 Realistically, I don't think we're going to do this. The DOM isn't threadsafe. 279560 4 ap 2010-09-15 08:44:00 -0700 The document is serialized to string for XSL transformation, so the actual transformation doesn't touch the DOM. As long as it's the transformation that takes most of the time here, it could be beneficial to use a separate thread. I'm not sure if it's realistic to expect that we work on this, and whether it's a practical issue. Safari doesn't beachball even on the example from comment 2 on modern desktop hardware. 279564 5 mail 2010-09-15 08:52:07 -0700 At Xopus we use some very complex XSLTs, and some of our clients have XSLTs that need optimization or are optimized for MSXML. Processing in those cases can take several seconds, and async support would definitely be very helpful to the Safari users and be a huge advantage over other browsers.