Bug 12863

Summary: WebKit does not implement window.stop()
Product: WebKit Reporter: Jeremy Volkman <jvolkman>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Enhancement CC: ap, beidson
Priority: P3 Keywords: InRadar
Version: 420+   
Hardware: All   
OS: All   
Attachments:
Description Flags
Proposed Fix none

Jeremy Volkman
Reported 2007-02-22 19:03:19 PST
Mozilla and Opera implement the window.stop() method which stops a window (frame or iframe) from completing a page load. IE provides similar functionality though its document.execCommand("Stop") call. It would be nice if WebKit provided this functionality.
Attachments
Proposed Fix (4.62 KB, patch)
2007-03-16 16:48 PDT, Brady Eidson
no flags
Alexey Proskuryakov
Comment 1 2007-02-23 03:44:25 PST
Confirmed. Are there any sites relying on this feature? What are the use cases for which it is necessary?
Jeremy Volkman
Comment 2 2007-02-23 05:06:24 PST
My particular use case is a component that uploads files to the server asynchronously. I'm writing a component for an Ajax web application framework (Echo2), and the component submits files to an off-screen iframe to prevent a full page refresh. In the supporting browsers, I use window.stop to give the ability to stop a file transfer. As of now in WebKit and KHTML there is no way to stop a transfer once it has started.
David Kilzer (:ddkilzer)
Comment 3 2007-03-14 03:00:08 PDT
Per comments in r20178, implementing window.stop() is now in Radar: <rdar://problem/5061826> http://trac.webkit.org/projects/webkit/changeset/20178
Brady Eidson
Comment 4 2007-03-14 11:04:27 PDT
Thats hilarious, I had no idea someone else was asking for it. It's something I might work on adding soon - if noone else takes it on.
Brady Eidson
Comment 5 2007-03-16 16:48:43 PDT
Created attachment 13676 [details] Proposed Fix
Brady Eidson
Comment 6 2007-03-16 17:00:36 PDT
Comment on attachment 13676 [details] Proposed Fix Anders reviewed this
Brady Eidson
Comment 7 2007-03-16 17:05:01 PDT
Landed in r20253
Note You need to log in before you can comment on or make changes to this bug.