Bug 82433 (KeyNoteHTML) - Webkit gets hung on exported as HTML from Keynote
Summary: Webkit gets hung on exported as HTML from Keynote
Status: RESOLVED INVALID
Alias: KeyNoteHTML
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified OS X 10.7
: P1 Major
Assignee: Nobody
URL: http://anyKeyNoteExportedHTML
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2012-03-28 00:30 PDT by Juan Falgueras
Modified: 2012-06-02 01:17 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Falgueras 2012-03-28 00:30:08 PDT 
Just export any iWork KeyNote to HTML and try to open it with WebKit.  It gets hung just in the first page before rendering it showing you an unending spinning icon.  Besides, you can open it perfectly with FireFox.
Comment 1 Alexey Proskuryakov 2012-03-28 11:39:45 PDT 
It seems that you're using something different than Safari 5.1.5. Please report bugs about unreleased versions of Safari via <http://bugreport.apple.com>.
Comment 2 Juan Falgueras 2012-03-29 02:25:28 PDT 
(In reply to comment #1)
> It seems that you're using something different than Safari 5.1.5. Please report bugs about unreleased versions of Safari via <http://bugreport.apple.com>.

I've used the last nightly built and I've updated to the last Safari 5.1.5.  Did you test the problem?
Comment 3 Alexey Proskuryakov 2012-03-29 08:55:38 PDT 
No, I haven't tested with Safari 5.1.5 and nightlies before. Indeed, this is reproducible in this configuration.
Comment 4 Alexey Proskuryakov 2012-03-29 08:55:49 PDT 
<rdar://problem/11024330>
Comment 5 Alexey Proskuryakov 2012-06-02 01:17:49 PDT 
Even though this is reproducible with Safari 5.1.x, it's nonetheless a result of running unreleased software on this system previously. It's unfortunate that that had such an effect even after uninstalling.

This is not a WebKit bug, so closing as INVALID per our policy. We'll keep tracking this internally at Apple.