.xpi: automatic -> compresses to zip, should expand (.xpi is zip)

[ProBackup-nl]

Mozilla Extension files are ending in .xpi which is a disguise for a zip file.

I would expect Keka version 1.1.3 (2809) in Automatic mode to extract the files inside.

What happens? The .xpi is compressed to a .zip file.

[aonez]

Added to the supported extraction list. Thanks for the tip! 👍

[gingerbeardman]

How about .IPA (also zip) and .JAR (also zip, I think)

[aonez]

How about .IPA (also zip) and .JAR (also zip, I think)

@gingerbeardman adding IPA too! JAR (along with APK and APPX) where added on 1.1.0 #170 (comment)

[gingerbeardman]

Could we also please add .safariextz (zipped legacy Safari Extension) @aonez

[alvarnell]

Those are going away very shortly, in the next WebKit.

…

Sent from my iPad

-Al-

On Apr 21, 2019, at 09:33, Matt Sephton ***@***.***> wrote: Could we also add .safariextz (zipped legacy Safari Extension) @aone.

[gingerbeardman]

Those are going away very shortly, in the next WebKit.

@alvarnell yes, support for them is being withdrawn, hence my use of "legacy".

But I will still have the need to work with old files on my drive, especially as I continue my efforts to port extensions to the horrid new app-extension mechanism. I'm still on 10.13 and Safari 11 because of extensions that I do not want to live without.

[alvarnell]

Not only support, they will no longer load with WebKit currently in test.

[gingerbeardman]

Not only support, they will no longer load with WebKit currently in test.

Yes, that's what I meant when I said they will not be supported.

The Safari/WebKit team have really screwed extension creators & users.

[aonez]

add .safariextz

Makes sense @gingerbeardman, now that they're legacy more than ever.

@alvarnell As far as I know the current version 12 of Safari already does not load extensions, only using the Extension Builder. I myself already had to rebuild an extension to be able to use it. Really sad about this, but extensions never got to a Firefox/Chrome feature capable level.

The Safari/WebKit team have really screwed extension creators & users.

Yep. I suppose the Extensions Gallery did not worked at all and bundling extensions in a container app and throw it to the MAS is easier for them.

[alvarnell]

Safari 12.1.1 is more selective about which extensions it loads, but I am still able to load many (all) as long as they come from the extensions gallery. Safari Technology Preview 12.2 won’t load any .safariextz and the option at the bottom of the Extensions preference window “Automatically update extensions from the Safari Extensions Gallery” has been removed. The only extension allowed must come from the Mac App Store.

…

-Al-

On Apr 23, 2019, at 01:47, aONe ***@***.***> wrote: @alvarnell <https://github.com/alvarnell> As far as I know the current version 12 of Safari already does not load extensions, only using the Extension Builder. I myself already had to rebuild an extension <https://github.com/aonez/GitHubCounter> to be able to use it. Really sad about this, but extensions never got to a Firefox/Chrome feature capable level. The Safari/WebKit team have really screwed extension creators & users. Yep. I suppose the Extensions Gallery did not worked at all and bundling extensions in a container app and throw it to the MAS is easier for them.