|Product:||WebKit||Reporter:||Pam Greene (IRC:pamg) <pam>|
|Component:||DOM||Assignee:||Pam Greene (IRC:pamg) <pam>|
|Version:||528+ (Nightly build)|
Description Pam Greene (IRC:pamg) 2009-03-11 17:53:49 PDT
Comment 1 Pam Greene (IRC:pamg) 2009-03-11 18:00:31 PDT
Created attachment 28508 [details] New test + result
Comment 2 Alexey Proskuryakov 2009-03-12 00:38:20 PDT
Comment 3 Alexey Proskuryakov 2009-03-12 04:36:13 PDT
Comment 4 Pam Greene (IRC:pamg) 2009-03-12 14:47:17 PDT
Comment 5 Pam Greene (IRC:pamg) 2009-03-12 14:50:24 PDT
To preempt questions: since location.href and location.replace() don't raise exceptions, the expected results don't change when these new cases are added.
Comment 6 Alexey Proskuryakov 2009-03-13 00:52:30 PDT
Comment 7 Adam Barth 2010-08-16 00:11:37 PDT
Yeah, we need a setTimeout after each location set. If you want to go faster, you can try using postMessage instead of setTimeout to trigger an async event.