RESOLVED FIXED 109550
DeleteButtonController::enable and disable should be called via a RAII object
https://bugs.webkit.org/show_bug.cgi?id=109550
Summary DeleteButtonController::enable and disable should be called via a RAII object
Ryosuke Niwa
Reported 2013-02-12 00:03:18 PST
DeleteButtonController::enable/disable should be wrapped in a RAII object. Introducing such a RAII object will also allow us to further reduce the number of if-defs for ENABLE_DELETION_UI.
Attachments
Cleanup (8.56 KB, patch)
2013-02-13 09:25 PST, Ryosuke Niwa
no flags
Cleanup (8.08 KB, patch)
2013-02-13 09:25 PST, Ryosuke Niwa
no flags
Fixed build (8.11 KB, patch)
2013-02-13 10:17 PST, Ryosuke Niwa
enrica: review+
Ryosuke Niwa
Comment 1 2013-02-13 09:25:15 PST
Ryosuke Niwa
Comment 2 2013-02-13 09:25:48 PST
WebKit Review Bot
Comment 3 2013-02-13 09:31:05 PST
Comment on attachment 188098 [details] Cleanup Attachment 188098 [details] did not pass cr-linux-debug-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16538176
Early Warning System Bot
Comment 4 2013-02-13 09:32:36 PST
Early Warning System Bot
Comment 5 2013-02-13 09:33:07 PST
EFL EWS Bot
Comment 6 2013-02-13 09:35:56 PST
Peter Beverloo (cr-android ews)
Comment 7 2013-02-13 09:36:44 PST
Comment on attachment 188098 [details] Cleanup Attachment 188098 [details] did not pass cr-android-ews (chromium-android): Output: http://queues.webkit.org/results/16538177
WebKit Review Bot
Comment 8 2013-02-13 10:00:26 PST
Comment on attachment 188098 [details] Cleanup Attachment 188098 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16454927
kov's GTK+ EWS bot
Comment 9 2013-02-13 10:04:03 PST
Ryosuke Niwa
Comment 10 2013-02-13 10:17:15 PST
Created attachment 188113 [details] Fixed build
Enrica Casucci
Comment 11 2013-02-13 11:50:29 PST
Comment on attachment 188113 [details] Fixed build View in context: https://bugs.webkit.org/attachment.cgi?id=188113&action=review Nicely done. Please address my comment before landing. > Source/WebCore/editing/markup.cpp:650 > + RefPtr<Range> updatedRangeRef = frame->editor()->avoidIntersectionWithDeleteButtonController(range); There is now nothing that checks here if the frame is not NULL. If the check was needed before I think you should add it.
Ryosuke Niwa
Comment 12 2013-02-15 12:01:13 PST
Ryosuke Niwa
Comment 13 2013-02-15 13:53:25 PST
Fixed one obvious error in my patch: http://trac.webkit.org/changeset/143048
Note You need to log in before you can comment on or make changes to this bug.