Closed rebloor closed 1 week ago
I think it's safe to assume that Chrome also supports these?
@caugner Why, they aren't documented in Chrome's reference content (https://developer.chrome.com/docs/extensions/reference/manifest/chrome-settings-override)
PS: Shouldn't those
{search,suggest}_url_{get,post}_params
features be subfeatures of{search,suggest}_url
?
@caugner no, they're all simply properties of the manifest key
I think it's safe to assume that Chrome also supports these?
@caugner Why, they aren't documented in Chrome's reference content (https://developer.chrome.com/docs/extensions/reference/manifest/chrome-settings-override)
Chrome does not support these. Extensions can put the get parameters in search_url
or suggest_url
if they want it in a cross-browser way.
Chrome's supported properties are documented at https://source.chromium.org/chromium/chromium/src/+/main:chrome/common/extensions/api/manifest_types.json;l=25-95;drc=636054fd874a8e9535b4db695c8ea15636200e52
Apologies, I drew the wrong conclusions, thanks for clarifying!
Summary
The manifest key chrome_settings_overrides
search_provider
object propertiessearch_url_get_params
andsuggest_url_get_params
were added in Bug 1496075 Support loading search extensions on startup but omitted from the BCDTest results and supporting details
See https://hg.mozilla.org/mozilla-central/rev/7efb082cc25d#l3.30
Related issues
MDN content changes in TBC