Extension size limit

[teknixstuff]

I've written an extension to allow using either the Chromium or Internet Explorer engine inside Pale Moon, however due to the need for it to include a lot of chromium files in it, the XPI is rather large (145MB). I attempted to upload this to addons.palemoon.org, however (after waiting a while for the upload), I get the error:

Unable to Comply
gfSuperVar - Upload of xpiUpload failed with error code: 1

Is there any solution to this, or is there a size limit on extensions on APMO?
If it helps, you can get the XPI file from https://github.com/teknixstuff/subwebvi ... ses/latest

[Moonchild]

You probably ran into the php POST limit. I've increased it to something that should allow a large upload like that. Can you try again?

[teknixstuff]

That didn't fix it, I still get the same error unfortunately.

[Moonchild]

That didn't fix it, I still get the same error unfortunately.

How long does your upload take? maybe it times out.
EDIT: I've increased the timeouts for it. they were relatively short.

[teknixstuff]

Same error again still.

[moonbat]

Same error again still.

I see you have submitted a bunch of extensions on the addons site, but none of us were appraised about it. You need to complete the metadata for your extensions and indicate the repository URL for the source code for the addons team to be able to review them properly. For example, your SumatraPDF extension lacks a homepageURL attribute in install.rdf, and the repository URL field is empty. Your teknixstuff.com webpage that you added in the support URL field just looks like a visiting card with zero information about any of these projects let alone any way to query for support.

For every new extension you submit, create a thread for it in the addons subforum; this can be used to announce new releases and for support queries for the extension. Add this thread in the support URL field, for example.

Take the requested information fields in the extension site seriously - they are not just there to simply fill in whatever you want or leave empty. An extension submitted requires the basics of a link to its source code repository and a way for people using it to contact you for support (which can be just a link to a thread on the addons page as I said).

[teknixstuff]

Sorry! I still haven't gotten round to finishing my site (unfortunately), that's why it looks rather empty. Still, I'll go and fix those issues.

[sidology]

I've written an extension to allow using either the Chromium or Internet Explorer engine inside Pale Moon, however due to the need for it to include a lot of chromium files in it, the XPI is rather large (145MB).

Interesting. I wonder is it possible to make a small version which will use local WebView (Edge) component?

[UCyborg]

I'd just like to point out that unless / until extension is implemented in a cross-platform manner, this should be added to install.rdf:

Code: Select all

<em:targetPlatform>WINNT_x86_64-msvc</em:targetPlatform>

So browser can block installation on non-compatible platforms, which are currently all that aren't 64-bit Windows.

[jars_]

It works for my Win7x64


... but can`t login, fkn ggl said "unsecure browser".

[back2themoon]

woring for me Win7x64

Isn't that 64-bit Windows?

[jars_]

On last figure, folders created by the extension (highlighted).
upd.
Hm. So maybe this is the reason? Extension must to create folders and write in to. But if Profile is not inside program folder ( i have it inside ) protection of Windows or antivirus is triggered. I bet on Win10 \ 11 and thear stupid quirks.

[teknixstuff]

I'd just like to point out that unless / until extension is implemented in a cross-platform manner, this should be added to install.rdf:

Code: Select all

<em:targetPlatform>WINNT_x86_64-msvc</em:targetPlatform>

So browser can block installation on non-compatible platforms, which are currently all that aren't 64-bit Windows.

Thanks, I'll add that. I'll probably also add a 32-bit build of it later. Ports to Linux and macOS aren't planned at this time though.

[jars_]

Need to turn off security.csp.enable = false To earn another site.
Settings Prefs.js for extension

Code: Select all

user_pref("extensions.subwebview.siteConfig", "[{\"pattern\":\"https://www.youtube.com/\",\"engine\":\"chromium\"},{\"pattern\":\"https://github.com/\",\"engine\":\"chromium\"},{\"pattern\":\"\",\"engine\":\"standard\"}]");

YouTube works fine, but Github is not, blocked by CSP

Code: Select all

Content Security Policy: The page’s settings blocked the loading of a resource at https://github.com/teknixstuff/subwebview (“default-src”).  
browserOverlay.js:110:17
Content Security Policy: The page’s settings blocked the loading of a resource at http://www.google.com/s2/favicons?sz=64&domain=github.com (“img-src”).  
browser.js:9821:22
Loading mixed (insecure) display content “http://www.google.com/s2/favicons?sz=64&domain=github.com” on a secure page[Learn More]  
browser.js:9821:22

And yet. Extension is very fragile, if you make a mistake with the pattern - it breaks everything .
("*" in the template was terrified by the code and poured a bunch of errors)
There is still no (I hope it will be) checking patterns. What would work only for addresses with "http" ignoring "addons: about:" and other service pages by default.
SfMBE

[teknixstuff]

Need to turn off security.csp.enable = false To earn another site.

CSP is still something I'm experimenting with solving, however afaik only the site's icon will be affected by a CSP block, as no other external resources are loaded by the page.

And yet. Extension is very fragile, if you make a mistake with the pattern - it breaks everything .
("*" in the template was terrified by the code and poured a bunch of errors)
There is still no (I hope it will be) checking patterns. What would work only for addresses with "http" ignoring "addons: about:" and other service pages by default.

You can use the blank pattern box (at the bottom) to select the default engine to be used, which will automatically apply to all HTTP and HTTPS pages. Alternatively, the correct pattern to match http sites would be

Code: Select all

http://*/*

[Moonchild]

I haven't been able to figure out yet why phoebus refuses the extension. PHP is set to accept large files, and has a long script timeout. nginx similarly has large file uploads enabled. phoebus itself doesn't log anything useful and doesn't throw, so no help there.

EDIT: double-checked everything, no hints. Even checked if it might be a UNIX socket limitation by tweaking relevant sysctl settings and temporarilky making it a tcp socket... no joy either.

So I'm really not sure what the issue is right now.

[Moonchild]

Okay, found the issue. only took me a few hours...

Please try again. It should work now.

*mutters something about Linux and 5 steering wheels*

[teknixstuff]

I'd just like to point out that unless / until extension is implemented in a cross-platform manner, this should be added to install.rdf:

Code: Select all

<em:targetPlatform>WINNT_x86_64-msvc</em:targetPlatform>

So browser can block installation on non-compatible platforms, which are currently all that aren't 64-bit Windows.

Is there a way to specify a minimum Windows version? The CEF 130 builds of this require Windows 10 or 11 currently.

[Moonchild]

I don't think the XPI installer has that kind of granularity for checking built in. you should probably put that check into the initialization of your extension, throwing an alert() or similar explaining the issue.

[teknixstuff]

I don't think the XPI installer has that kind of granularity for checking built in. you should probably put that check into the initialization of your extension, throwing an alert() or similar explaining the issue.

Okay, will do.