More generally, Safari App Extensions will always be fighting an uphill battle when it comes to adoption, because (1) they are very limited in what they can do (see above) and (2) they are different than every other browser. This is not possible with a Safari App Extension. When the user saves the recipe (or cancels), we close the window that we opened. In Chrome and Firefox, when the user clicks a browser toolbar button to import a recipe, we open a new window that shows the recipe and allows them to edit it before saving. Use case: our browser extension which allows users to import recipes, which is available here: It is not possible to set the size or position of a browser window opened by a Safari App Extension. It is not possible to close a browser tab or window via a Safari App Extension, even if the tab or window was opened by the extension.
#1password safari technology preview upgrade
In our case, we're just including a version number in requests made by our extension, and when we issue a new version we'll present a message to our users telling them to upgrade manually, because I don't want to deal with the hassle and uncertainty of the Safari Extensions Gallery. There are still extensions in there that are being used by tons of people, like 1Password and AdBlock Plus, so presumably it is alive and they are still accepting submissions. I don't know about the Safari Extensions Gallery. If they stopped supporting legacy extensions right now, without making major changes to Safari App Extensions, then they'd basically be killing Safari as a browser for anyone that is even remotely a power user, given that Safari App Extensions have almost no uptake. I don't see how Apple can stop supporting legacy extensions without making significant improvements to Safari App Extensions (i.e., doing whatever is necessary for an app like 1Password to be able to adopt them). If they stop supporting legacy extensions, then they'll be killing the Safari integration for 1Password, Evernote, Pocket, and many other important applications. I'm wondering if it's worth the trouble of building a completly separate app extension for Safari, or if we can continue using the Safari Extension builder? This seems like a massive hurdle compared to Chrome, Firefox, and Opera who all support the same WebExtensions API. I see the "suggested" way of doing this is now to create a Safari App Extension in Xcode, which requires building the extension primarily in Xcode and involves learning Swift (or Objective-C). Some background: I'm a web developer and would like to create a new version of my Safari Extension. If yes, how soon do existing Safari Extensions need to be transitioned to a Safari App Extension? AKA: How long until my Safari Extension breaks or is no longer supported for new users?.
0 kommentar(er)
