Firefox mobile Options synchronize and Options Import. Do they work for you?

[paponius]

Before issuing an issue, can somebody check if %subj works for them?
I only tried on one mobile/instance of FF.

• Importing Options from a saved JSON has no effect (while on PC doing the same was working as expected)
• turning on synchronize has no effect (expected Options sync from PC instance, using the same account)

In connection with the above,

• a reaction to successful Options import would be nice.
• an easier way to chnge hidden options
  I guess you don't want to put options like userScriptEnabled on the standard Options page for an average user to not understand,
  but what about adding such options, or a full JSON editor on
  moz-extension://cd03885e-2c2c-4c35-8907-4a7e5e7e8af0/src/ui/pages/options.html?advanced
  or
  moz-extension://cd03885e-2c2c-4c35-8907-4a7e5e7e8af0/src/ui/pages/advanced_options.html
  without any direct link, so an user would still have to edit the URI to access it, but still easier than exporting, editing, importing JSON on a mobile.

Thanks

[gildas-lormeau]

The import issue is known. It's due to a technical limitation in Firefox mobile that I cannot circumvent. I think I need to integrate some kind of text editor in a "Advanced configuration" tab because this is the second time someone is talking about this problem.
I didn't know the "sync" option did not work, I'll do some tests.

[paponius]

yes, Firefox is currently blocking all local file access. I wondered if it was possible from an extension. So, it's not. Quite limiting.

Thank you for looking into the sync Options feature and considering "Advanced configuration" page.
For now it seems I can't enable userScriptEnabled without rooting the phone and searching FF data dir for it.

Would you like me to file the Issue about the mobile sync Options not working, for posterity?
P.S. I did not test it with another phone and account.

[gildas-lormeau]

Feel free indeed to file an issue for the "sync" bug, it'll help me keep track.

For the record, userScriptEnabled is disabled by default for privacy reasons. Enabling it by default would expose the SingleFile events to all pages.

[paponius]

I am not sure there may be a safety issue, unless enabling userScriptEnabled would make an object of SingleFile available,
or SingleFile does in some way process the single-file-on-before-capture-response event's properties.

UserScripts could still run on a page and do bad stuff (or good) before a page, including such modifications, is saved. (e.g. change visible text, or inject harmful JS) Doing a bad stuff upon the event would not make them more harmful.

On the other hand, I agree it's a good idea to disable it by default and hide the option to enable such feature. As per minimizing the attack surface.

Btw, my script is an obfuscator. My colleague was saving pages and sharing them when I noticed he include their personal/login data in tags. It's working OK and thanks to the SingleFile events it could restore everything after saving and he can continue to use the web page as it was before the save.

sync not working filed: #1668