You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would appreciate the ability to type into the address bar.
From #15126, I understand this is currently not possible and seems out of scope. The author of that issue never got back to the question about use case. This would help test implementations of the omnibox API in Edge, Chrome, and Firefox extensions.
Even if exposing suggest results is deemed out of scope, the ability to send keyword some text[enter], where keyword is the keyword that triggers an extension (defined in the manifest) and some text is the text to be handled by onInputEntered, would help extension developers test basic functionality.
This would enable more complete testing of extensions for Edge, Chrome, and Firefox. For example, in my doi-resolver project, there is currently no way to test omnibox API usage.
The text was updated successfully, but these errors were encountered:
@yury-s - for what it's worth, omnibox is included in w3c/webextensions interfaces: interfaces/chromium/chrome-common-extensions-api/omnibox.json. Playwright is one of the very few options extension developers have for testing extensions (the other being manual pairing of puppeteer with a testing framework like jest or mocha), so I hope the team will keep an open mind about supporting this neglected community.
🚀 Feature Request
I would appreciate the ability to type into the address bar.
From #15126, I understand this is currently not possible and seems out of scope. The author of that issue never got back to the question about use case. This would help test implementations of the omnibox API in Edge, Chrome, and Firefox extensions.
Even if exposing suggest results is deemed out of scope, the ability to send
keyword some text[enter]
, wherekeyword
is the keyword that triggers an extension (defined in the manifest) andsome text
is the text to be handled byonInputEntered
, would help extension developers test basic functionality.Example
Motivation
This would enable more complete testing of extensions for Edge, Chrome, and Firefox. For example, in my doi-resolver project, there is currently no way to test omnibox API usage.
The text was updated successfully, but these errors were encountered: