Summary: | REGRESSION: webViewDidChange: posted even when should* delegates reply NO | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Duncan Wilcox <duncan> | ||||||
Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | mrowe | ||||||
Priority: | P1 | Keywords: | InRadar, Regression | ||||||
Version: | 420+ | ||||||||
Hardware: | Mac | ||||||||
OS: | OS X 10.4 | ||||||||
Attachments: |
|
Description
Duncan Wilcox
2006-07-27 06:52:19 PDT
Regression->P1 Created attachment 9971 [details]
DumpRenderTree patch
Submitting this for feedback. This patch adds support for having the DumpRenderTree editing delegate respond NO to should* requests, for example with something like this:
Index: LayoutTests/editing/deleting/delete-by-word-001.html
===================================================================
--- LayoutTests/editing/deleting/delete-by-word-001.html (revision 15828)
+++ LayoutTests/editing/deleting/delete-by-word-001.html (working copy)
@@ -62,6 +62,8 @@
</div>
<script>
+if(window.layoutTestController)
+ window.layoutTestController.setAcceptsEditing(false);
runEditingTest();
</script>
This should perhaps initially only be enabled only on layout tests using the eventSender mechanism, as that path is more conformant to delegate requests (as opposed to the JS one).
I have a regression similar to the one in this bug where scrolling through text with arrow keys happens even if the delegate responds NO, should be relatively easy to build a test case.
Created attachment 9974 [details]
DumpRenderTree patch
Ooops, reset the acceptsEditing flag on each new test.
Comment on attachment 9974 [details]
DumpRenderTree patch
Looks OK.
Formatting of this:
+ if(acceptsEditing) {
does not match our standard, and there is code here with braces around single-line blocks that also does not match it.
r=me
Comment on attachment 9974 [details]
DumpRenderTree patch
I cut this down quite a bit before landing it, but it still should be sufficient to allow a test to be written.
Committed revision 15904.
Clearing the review flag on this so we can now use this bug report to fix the bug reported.
radar 4823005 |