Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(121)

Unified Diff: chrome/browser/ui/webui/omnibox/omnibox.mojom

Issue 509173003: Omnibox.mojom: make input_string non-nullable. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 6 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/ui/webui/omnibox/omnibox.mojom
diff --git a/chrome/browser/ui/webui/omnibox/omnibox.mojom b/chrome/browser/ui/webui/omnibox/omnibox.mojom
index 81736526472bae6b20092db05b745e74511cbb44..262ae76773c1ff1ba493ceee76277eb6f5335f55 100644
--- a/chrome/browser/ui/webui/omnibox/omnibox.mojom
+++ b/chrome/browser/ui/webui/omnibox/omnibox.mojom
@@ -49,10 +49,7 @@ struct OmniboxResultMojo {
[Client=OmniboxPage]
interface OmniboxUIHandlerMojo {
- // TODO(yzshen): Conceptually |input_string| could be non-nullable. However,
- // crbug.com/407258 (JavaScript encoder encodes empty string as null) prevents
- // us from doing so. Change it into non-nullable once the bug is resolved.
- StartOmniboxQuery(string? input_string,
+ StartOmniboxQuery(string input_string,
int32 cursor_position,
bool prevent_inline_autocomplete,
bool prefer_keyword,
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698