<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[New (sort of) in Chromium: Settings Overrides API - custom default search engines soon possible?]]></title><description><![CDATA[<p dir="auto">Settings Overrides</p>
<p dir="auto">Settings overrides are a way for extensions to override selected Chrome settings. The API is available on Windows in all current versions of Chrome and is available on Mac in Chrome 56 and later.</p>
<p dir="auto">Homepage, Search Provider, and Startup Pages<br />
Here is an example how homepage, search provider and startup pages can be modified in the extension manifest. Web sites used in the settings API must be verified (via Webmaster Tools) as being associated with that item in the Chrome Web Store. Note that if you verify ownership for a domain (for example, <a href="http://example.com" target="_blank" rel="noopener noreferrer nofollow ugc">http://example.com</a>) you can use any subdomain or page (for example, <a href="http://app.example.com" target="_blank" rel="noopener noreferrer nofollow ugc">http://app.example.com</a> or <a href="http://example.com/page.html" target="_blank" rel="noopener noreferrer nofollow ugc">http://example.com/page.html</a>) within your extension.</p>
<p dir="auto">For external extensions, the search_provider, homepage and startup_pages URL values can be parametrized using a registry key. A new registry entry should be created next to the "update_url" key (see instructions here). The value name is "install_parameter", the value data is an arbitrary string:</p>
<p dir="auto"><strong>MORE HERE:</strong> <a href="https://developer.chrome.com/extensions/settings_override" target="_blank" rel="noopener noreferrer nofollow ugc">https://developer.chrome.com/extensions/settings_override</a></p>
<p dir="auto">Custom default search engines soon possible?</p>
]]></description><link>https://forums.opera.com/topic/22035/new-sort-of-in-chromium-settings-overrides-api-custom-default-search-engines-soon-possible</link><generator>RSS for Node</generator><lastBuildDate>Fri, 14 Aug 2026 13:56:22 GMT</lastBuildDate><atom:link href="https://forums.opera.com/topic/22035.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 31 Jul 2017 01:11:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to New (sort of) in Chromium: Settings Overrides API - custom default search engines soon possible? on Tue, 01 Aug 2017 00:11:59 GMT]]></title><description><![CDATA[<p dir="auto">Of course that would/will be limited to what extent extensions could override. Interesting is that at the same time Chrome is taking measures how to get users more engaged and responsible of extensions they get.</p>
]]></description><link>https://forums.opera.com/post/125626</link><guid isPermaLink="true">https://forums.opera.com/post/125626</guid><dc:creator><![CDATA[[[global:former_user]]]]></dc:creator><pubDate>Tue, 01 Aug 2017 00:11:59 GMT</pubDate></item><item><title><![CDATA[Reply to New (sort of) in Chromium: Settings Overrides API - custom default search engines soon possible? on Mon, 31 Jul 2017 23:29:12 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto">Custom default search engines soon possible?</p>
</blockquote>
<p dir="auto">I don't think so, at least not through extensions.</p>
]]></description><link>https://forums.opera.com/post/125624</link><guid isPermaLink="true">https://forums.opera.com/post/125624</guid><dc:creator><![CDATA[leocg]]></dc:creator><pubDate>Mon, 31 Jul 2017 23:29:12 GMT</pubDate></item><item><title><![CDATA[Reply to New (sort of) in Chromium: Settings Overrides API - custom default search engines soon possible? on Mon, 31 Jul 2017 23:09:38 GMT]]></title><description><![CDATA[<p dir="auto">anyone?</p>
]]></description><link>https://forums.opera.com/post/125622</link><guid isPermaLink="true">https://forums.opera.com/post/125622</guid><dc:creator><![CDATA[[[global:former_user]]]]></dc:creator><pubDate>Mon, 31 Jul 2017 23:09:38 GMT</pubDate></item></channel></rss>