[bug] zoom.minPercent > 100

[biopsin]

I've noticed that if I set a zoom.minPercent value above 100 and after restarting of PM,
error is printed in console after 5 sec

Timestamp: 03/10/2020 12:06:38 PM
Error: A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/J ... sm/Promise

Date: Tue Mar 10 2020 12:06:34 GMT+0100 (CET)
Full Message: 2147942487
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: register :: line 194
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: process :: line 968
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: scheduleWalkerLoop/< :: line 747

[adesh]

That looks like a very generic error message and can be caused in a lot of situations which can throw exceptions. Are you sure you don't see this error if you reset minPercent?

[therube]

If you reset zoom.minPercent, then the messages are not logged.

[biopsin]

I would not post this otherwise.
Can I read from your comments that you both tested it and you both don't see this in console?

[Moonchild]

The important part of the message (the code location) was not included in your posted error message.

I'm pretty sure what happens here is that by setting this value, the default zoom value (100%) falls outside of the acceptable range which causes a failure on a deferred task.
Why are you setting this to > 100% to begin with? There is no reason for that as it indicates your overall minimum allowed zoom level which should always be 100 or less (same with max, which should always be 100 or more).

[biopsin]

Hey,
You mean in about:config?
Since I switched to a 4K 32" monitor all pages are uber-tiny, setting minimum zoom to 170, I can quickly zoom in on page with ctrl-0.
So how come zoom.maxPercent is set at 300% without error in console?.

[Moonchild]

The correct solution is setting your system's DPI to the proper value, so "100%" is normal size.

So how come zoom.maxPercent is set at 300% without error in console?.

...because max should be > 100 which it is.

[biopsin]

I did check with xrandr and also included the output of cvt -r 3840 2160 60 into xorg.conf for the sake of it, but I don't see any difference.
will continue tinker with the system some more, if not guess I'll leave 170 and ignore the message in console, at least I know why it's printed.

[Moonchild]

I'm not a Linux person so I don't know what that command does but it doesn't seem to actually do anything for dpi (which at your screen size and res should be set higher than whatever is default, since your pixel density is considerably higher).

[Lootyhoof]

You could set layout.css.devPixelsPerPx to 1.70 in about:config to get a similar effect.

[biopsin]

You could set layout.css.devPixelsPerPx to 1.70 in about:config to get a similar effect.

I could, but it scales everything up and PM window is fine as it is..
it also works setting toolkit.zoomManager.zoomValues with fewer values;
ctrl+ jumps straight to 170% and ctrl+mousewheel for finnishing touches if needed.
Anyways thanks for the suggestion and feedback.