Browser configuration does not store integer values

Bug Reports
, ,
1

REPRODUCIBILITY (% or how often): 100%
BUILD ID: 3.3.016 (Rokua)
HARDWARE (Jolla, Tablet, XA2,…): Jolla C, Xperia X
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?): Yes

DESCRIPTION:

Whenever modifying an integer value in browser about:config the new value does not get saved. (Strings and booleans work fine)

PRECONDITIONS:

unknown

STEPS TO REPRODUCE:

  1. open browser
  2. enter address about:config
  3. accept warning
  4. enter filter: network.proxy.http
  5. enter a valid IP address in for network.proxy.http
  6. enter a valid port number (e. g. 8080) for network.proxy.http_port
  7. Tap accept
  8. Open about:config again, enter the same filter and verify the values

EXPECTED RESULT:

  1. The values entered before have been stored

ACTUAL RESULT:

  1. Changes to the address field have been stored but changes to the port field are lost

ADDITIONAL INFORMATION:

Same behaviour affects also other integer settings, e. g. network.proxy.type

This still worked correctly in Nuuksio.

2

As a workaround, you can set these values in /home/nemo/.mozilla/mozembed/prefs.js (make sure the browser is not running!):

Example:

user_pref("network.proxy.http", "127.0.0.1");
user_pref("network.proxy.http_port", 8118);
user_pref("network.proxy.no_proxies_on", "localhost, 127.0.0.1, 192.168.0.0");
user_pref("network.proxy.proxy_over_tls", false);
user_pref("network.proxy.type", 1);
3 Likes
3

Because the browser can take a long time to really exit especially on Jolla C (or actually loop forever), maybe those commands are best used for that purpose

systemctl --user status booster-browser
systemctl --user stop booster-browser
systemctl --user start booster-browser

Thanks, that does does the trick.

4

Thanks for reporting this @ugeuder. This should now be fixed in the latest browser on 4.4.0 and later.

I’ve tagged it as “fixed”, but if you think this is incorrect (e.g…if you still experience this issue) then please say and we can look at it again.

5

Probably related : some statements in prefs.js are ignored. For example this one: user_pref(“browser.privatebrowsing.autostart”, true);

6

I can report that the problem is fixed for the abovementioned preferences in 4.4 on 10 II. However, I have noticed that changing the layout.css.devPixelsPerPx property in config , prefs.js, and user.js is not working. Changing it in about:config is working until the next start of the browser, prefs.js is being overwritten and user.js is not being applied at all (as it does for other properties like network.proxy.HTTP). Is there anything special with layout.css.devPixelsPerPx? Unfortunately without this property I cannot see any way to change the font size in the browser.

7

This will fix the dexPixelsPerPx and friends as well

2 Likes
8

The bug has been fixed for a long time, but I came back here to use the work-around instructions.They might still be useful for all kind of hackery :slight_smile:

Well, if they would still work, so let me update them (Sailfish OS 4.6.0.11 (Sauna))

The settings file is now located at /home/nemo/.local/share/org.sailfishos/browser/.mozilla/prefs.js

The browser runs as an instantiated unit: systemctl status --user booster-browser@sailfish-browser