[tags:wwdc20-10649]

Will we still have to wrap Safari Extensions inside a macOS app? I don't have a macOS app. I just have an extension I'd like to bring to Safari in the same way I have for Chrome, Firefox, and Edge.

We have an extension that requires payment after a 14 day free trial. If Safari extensions are accessible via the AppStore does that mean Apple expects revenue share from developers?

Does Safari Web Extensions include Private Browsing? Will my extension still work when the user is Private/Incognito browsing? Thanks!

Will Safari support the WebApi Manifest v3 extension standard? And if so when will it be implemented?

After years of using private API and not being in the Mac App Store, I was really excited Monday when I heard that Safari was adopting Web Extensions. Unfortately when I installed the betas and ran the converter on my Firefox/Chrome/Opera/Brave/Vivaldi/Edge extension, I was told that the browser.bookmarks - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks API was not yet supported. I have patiently filed many bugs on this over the years: 10473679, 22932240, 32608461, 49706819, and now FB7772296. Users want bookmarks management beyond what is offered in Safari, and some users want to sync their bookmarks with other browsers. Currently, there are others’ apps, and do-it-yourself users who try and do this by overwriting the Bookmarks.plist file, with disastrous results to their iCloud account. I hope that the omission of browser.bookmarks - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks from Safari Web Extensions was due to disruptions cau

I have an app that primarily revolves around a WKWebView. A community has created quite a few browser extensions around the website that my app as a client for. I would love to allow users to incorporate those extensions easily. Is there a way to do that?

I downloaded and installed the Xcode 12 Beta in hopes of trying out the Web Extension converter tool. I ran: xcrun safari-web-extension-converter /path/to/my/extension and got the following error: xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find safari-web-extension-converter 2> /dev/null' failed with exit code 17664: (null) (errno=No such file or directory) xcrun: error: unable to find utility safari-web-extension-converter, not a developer tool or in PATH This seems to indicate I'm running the Xcode 11 version of xcrun (which I also have on my machine) which doesn't have the tool. The path to xcrun was /usr/bin/xcrun. How do I run the 12 Beta version of xcrun so I can run the Converter tool? Or do I need to uninstall v11? I thought you could run both at the same time. Thanks! Chris

The following keys in your manifest.json are not supported by your current version of Safari. If these are critical to your extension, you should review your code to see if you need to make changes to support Safari: storage webRequestBlocking incognito privacy What am I supposed to use for webRequestBlocking with Safari? (Seems this would be one of the most desired keys for web extensions?)

In her WWDC20 talk, Ellie Epskamp-Hunt mentioned in passing that you should assume that just because DOMContentLoaded has occurred that the script is loaded (for example, user might have to give it permission to load). But she doesn't say how you should determine that the script has loaded. How should you do that?

In some applications, a Safari Web Extension must receive a Native Message and process it in the background, without activating Safari. For example, assuming that Safari Web Extensions will soon support the browser.bookmarks API - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks, when a bookmarks syncing application needs to push a new bookmark from a source of truth into Safari's bookmarks, it will send a Native Message to the extension, and this may happen when Safari is not the active macOS application, for example if the user is writing email in Mail. I am modifying Apple's Sea Creator - https://developer.apple.com/documentation/safariservices/safari_web_extensions/developing_a_safari_web_extension sample code to establish a proof of concept for such an application. So far, pretty good. I am able to send over 150 MB of data – far more than will be needed – from the app, to the extension's background.js script, and vice versa. However, it seems when Safari receives the m

We currently have a working Safari App Extension that was converted from a Chrome extension. We want to migrate to a Safari Web Extension so that we can have a unified code base. My question is with packaging the extension in the container app. Ideally we'd like to package both the old App Extension and the new Web Extension in the same container app, so that we can support both Safari 13 and 14. However, when users are using Safari 14 we'd like them to see only the Web Extension and not the old App Extension. Is there a way to do this?

At present I have safari app extension which supports macOS version 10.13. 6 and 10.12. If i switch to Safari web extension, their support will be lost. Is there any plan for deprecation of safari app extension.

I am on BigSur beta, safari 14 and xcode 12 beta 2. When i run the command: xcrun safari-web-extension-converter /path/to/my/extension I get this error: xcrun: error: unable to find utility safari-web-extension-converter, not a developer tool or in PATH

I have working cross-platform extension which I converted for Safari using xcrun safari-web-extension-converter PATH. Goal of extension is to bookmark any URL into my website account. My extension is perfectly working fine for Chrome but for Safari version, everything works well if user allows access permission for every website. The case is, when user presses extension button, we are checking user is logged into its account or not by opening our website URL into another tab. var openSignin = function openSignin() { tconsole.log('hey'); tchrome.tabs.create({ url: _config.baseURL + '?extension=1', active: false }); }; When this AUTH tab is loaded, following method will be called as it happens in Chrome which in turn extracts public and private tokens generated when any user logs into our website. chrome.tabs.onUpdated.addListener(function (tabID, changeInfo, tab) { if (tab.status == 'complete' && tab.url.startsWith(_config.baseURL)) { chrome.tabs.executeScript(tab.id, { code: 'localStorage.getItem(PUBL

I am able to convert my extension to via XCode 12 Beta and it works great. However, I am very unclear of backward compatibility. Right now it needs Safari 14 only and its not shown on Safari 13 . So, will I be able to distribute my extension for Safari 13 as well? Or do I have any other option for Backward compatibility?