Issue metadata
Sign in to add a comment
|
Align behavior of window.external.IsSearchProviderInstalled and window.external.AddSearchProvider with the spec |
||||||||||||||||||||||||||||||||
Issue descriptionChange description: window.external.IsSearchProviderInstalled and window.external.AddSearchProvider will both be defined as methods that are no-ops. Changes to API surface: - Add back AddSearchProvider (removed in issue 542487 ), with a no-op implementation. - Change IsSearchProvider() to be a no-op implementation as well. Links: Public standards discussion: https://github.com/whatwg/html/issues/713 Support in other browsers: Internet Explorer: No-ops in IE10, though the documentation notes that AddSearchProvider [1] always returns S_OK in IE10 and IsSearchProviderInstalled [2] always returns 2 in IE10. Firefox: Firefox 2+, though the documentation notes that this feature may be removed at any time [3]. Safari: none [1] https://msdn.microsoft.com/en-us/library/aa744112(v=vs.85).aspx [2] https://msdn.microsoft.com/en-us/library/aa342526(v=vs.85).aspx [3] https://developer.mozilla.org/en-US/docs/Web/API/Window/sidebar/Adding_search_engines_from_Web_pages
,
Jul 28 2016
(I have no idea how this works, so hopefully I'm setting the right flags?)
,
Aug 28 2017
,
Sep 12 2017
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues. We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate. For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit For any questions, please contact owencm, sshruthi, larforge
,
Mar 15 2018
|
|||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Jul 28 2016