Space after keyword shouldn't trigger omnibox extension
Reported by
oct...@gmail.com,
Jun 12 2016
|
|||||||
Issue descriptionChrome Version : 51.0.2704.84 (Official Build) (64-bit) What steps will reproduce the problem? (1) Make an omnibox extension by registering the keyword "foo" in manifest.json (2) Type "foo" into omnibox. Then type space. (3) The omnibox extension is triggered. What is the expected result? The extension is only triggered by pressing TAB after entering the keyword. What happens instead? The extension is triggered by pressing SPACE after entering the keyword. Please provide any additional information below. Attach a screenshot if possible. I'm making an omnibox extension for NPM so I registered the keyword NPM. However I also rely on omnibox to access Google search. Now whenever I want to search something, like "npm how to install a package", I'll be screwed.
,
Jun 13 2016
Able to reproduce the issue on Windows 7, Mac 10.11.5, Ubuntu 14.04 using 51.0.2704.84, latest canary 53.0.2766.0 with below steps: 1.Loaded given foo unpacked extension to chrome://extensions. 2.Typed keyword 'foo' and hit space->observed that extension triggered. Please find attached screencast. This is non regression issue seen from M-30(30.0.1549.0). Hence, marking it as untriaged. Could anyone from dev team look into this issue please.
,
Jun 13 2016
This is working as intended. It's a very common way people use to (intentionally) enter keyword mode / enter custom search engine mode / trigger an omnibox extension. There are several possible workarounds: - (as you noted) change the name of the keyword - press backspace after the space. This should get you out of keyword mode yet keep the space still around so you can keep typing - type a question mark "?" before typing your search. This puts you in "forced query" mode which means the input will not be interpreted as a keyword or the beginning of a URL. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by oct...@gmail.com
, Jun 12 2016