RESOLVED FIXED 37837
[chromium] Select popups should be closed when the browser window is moved/resized.
https://bugs.webkit.org/show_bug.cgi?id=37837
Summary [chromium] Select popups should be closed when the browser window is moved/re...
Jay Civelli
Reported 2010-04-19 18:30:23 PDT
In Chromium, open a select popup. Move the browser window while the popup is showing. Expected: The popup is closed. Actual: The popup still shows.
Attachments
Make a unique method to close all popups. (3.64 KB, patch)
2010-04-19 18:37 PDT, Jay Civelli
fishd: review-
Preserve the old API so it does not break the Chromium build (2.60 KB, patch)
2010-04-22 17:26 PDT, Jay Civelli
no flags
Jay Civelli
Comment 1 2010-04-19 18:37:20 PDT
Created attachment 53758 [details] Make a unique method to close all popups.
Darin Fisher (:fishd, Google)
Comment 2 2010-04-21 14:58:57 PDT
Comment on attachment 53758 [details] Make a unique method to close all popups. > Index: WebKit/chromium/public/WebView.h > - // DEPRECATED: WebView::hideSuggestionsPopup is the new way to access this. > - virtual void hideAutofillPopup() = 0; > - > - // Hides the suggestions popup if any are showing. > - virtual void hideSuggestionsPopup() = 0; > + // Hides any popup (suggestions, selects...) that might be showing. > + virtual void hidePopups() = 0; Won't this break Chromium when it is committed? Can you preserve the old method(s) until Chromium is switched over to only calling hidePopups? Then circle back with a cleanup patch to remove the DEPRECATED methods. Otherwise, LGTM
Jay Civelli
Comment 3 2010-04-22 17:26:59 PDT
Created attachment 54113 [details] Preserve the old API so it does not break the Chromium build
WebKit Commit Bot
Comment 4 2010-04-27 19:08:43 PDT
Comment on attachment 54113 [details] Preserve the old API so it does not break the Chromium build Clearing flags on attachment: 54113 Committed r58369: <http://trac.webkit.org/changeset/58369>
WebKit Commit Bot
Comment 5 2010-04-27 19:08:47 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.