RESOLVED FIXED 56674
Convert fake-drag into a dumpAsText test and remove 1s timeout
https://bugs.webkit.org/show_bug.cgi?id=56674
Summary Convert fake-drag into a dumpAsText test and remove 1s timeout
Tony Chang
Reported 2011-03-18 13:46:59 PDT
Convert fake-drag into a dumpAsText test and remove 1s timeout
Attachments
Patch (26.93 KB, patch)
2011-03-18 13:49 PDT, Tony Chang
eric: review+
Tony Chang
Comment 1 2011-03-18 13:49:37 PDT
Tony Chang
Comment 2 2011-03-18 13:50:08 PDT
http://trac.webkit.org/changeset/10620 originally added this test.
Tony Chang
Comment 3 2011-03-18 13:50:33 PDT
Also, this is one of the slowest editing tests.
Eric Seidel (no email)
Comment 4 2011-03-18 14:05:11 PDT
Comment on attachment 86205 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=86205&action=review OK. > LayoutTests/editing/selection/fake-drag.html:23 > - window.setTimeout(step7, 1); > + window.setTimeout(step7, 0); This is 1ms, no? Why make it 0?
Eric Seidel (no email)
Comment 5 2011-03-18 14:06:13 PDT
Letting the authors of this test see this go by.
Tony Chang
Comment 6 2011-03-18 14:13:51 PDT
(In reply to comment #4) > (From update of attachment 86205 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=86205&action=review > > OK. > > > LayoutTests/editing/selection/fake-drag.html:23 > > - window.setTimeout(step7, 1); > > + window.setTimeout(step7, 0); > > This is 1ms, no? Why make it 0? Since JS timers are 4ms, I think any value under 4 will behave the same. I just wanted to make it explicit that we were running these as fast as possible. Actually, we could probably just write this test without any of the setTimeouts. Let me know if you think that would be clearer.
Eric Seidel (no email)
Comment 7 2011-03-18 14:16:58 PDT
(In reply to comment #6) > > This is 1ms, no? Why make it 0? > > Since JS timers are 4ms, I think any value under 4 will behave the same. I think you're right. >I just wanted to make it explicit that we were running these as fast as possible. Actually, we could probably just write this test without any of the setTimeouts. Let me know if you think that would be clearer. Ideally we'd remove the setTimeouts, but I wouldn't worry about it.
Tony Chang
Comment 8 2011-03-18 14:31:11 PDT
(In reply to comment #7) > (In reply to comment #6) > >I just wanted to make it explicit that we were running these as fast as possible. Actually, we could probably just write this test without any of the setTimeouts. Let me know if you think that would be clearer. > > Ideally we'd remove the setTimeouts, but I wouldn't worry about it. I tried this, but it turns out that we need setTimeouts or the editing delegate won't dump selection changes. I'll just leave the timeouts in the test.
Tony Chang
Comment 9 2011-03-21 14:39:49 PDT
Note You need to log in before you can comment on or make changes to this bug.