1796788 - Disable extension keyword handling when a search engine keyword has already been entered in URL

Status: RESOLVED DUPLICATE of bug 1815819

(Firefox :: Address Bar, defect)

Description

[Elouan Martinet]

Attachment: 22-10-21-16-13-13-030380100.png

Steps to reproduce:

• Create a fresh profile
• Install an extension that defines a keyword (omnibox API), e.g. https://addons.mozilla.org/en-US/firefox/addon/awesome-emoji-picker/
• Type [search engine keyword] [extension keyword] in the URL bar, e.g. @google emoji foo
• (Optional) Press enter

Actual results:

• Extension keyword handling works even if a search engine keyword has already been entered in the URL bar
• Pressing enter will trigger whatever action the extension has defined for this keyword (just like it would without entering a search keyword)

Expected results:

• Extension keyword handling is disabled upon entering a search engine keyword in the URL bar
• You can search for keywords even if that keyword is registered by an extension (using omnibox object attribute in their manifest) when pressing enter

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Elouan Martinet]

Bookmark keywords are unaffected by this issue.

Comment 3

[rugk]

Add-on dev of the mentioned extension here. The downstream issue/related issue for that is https://github.com/rugk/awesome-emoji-picker/issues/139. Actually, the issue here, is clearly a Firefox bug though, as two keywords should not be possible, respectively one needs to take precedence. (which, IMHO, should be the first one, but you may find another solution)

The keyword is statically defined in the extension, after all.

Comment 4

[Cristian Baica [:cbaica], Release Desktop QA]

This doesn't look like a new regression. It's been like this all the way back to the implementation of search mode for engines(Fx81), meaning that the extension is always suggested even if the user is already in searchmode.
The double keyword seems to be working only in case of webextensions, because it doesn't work with double keywords of default search engines. Marking the bug as new.