You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the workaround mentioned in this thread to fix the problem of not being able to add separators between buttons on the toolbar. Here's a pix of what they look like in customize mode:
However, Waterfox now resizes itself on opening and looks like you see it in the image. I don't know whether the spaces are the cause of it though.
My system is Windows 8.1 patched using security only updates every month rather than the rollups containing telemetry and other Microsoft bloatware just in case that's relevant.
The text was updated successfully, but these errors were encountered:
I've found the reason why Waterfox was resizing itself as shown in the screenshot above. It has nothing to do with the separators, but rather a config setting namely this one: privacy.resistFingerprinting
When set to true in about config, Waterfox resizes itself on opening.
Resetting it to its default value allows Waterfox to open normally.
The config setting itself is the second one down in the "Getting Started" recommendations on this site
From the accepted answer to fingerprinting - Why does Tor Browser screen size vary across monitors? - Tor Stack Exchange:
… privacy.resistFingerprinting to true to use the client content window size … In addition, we prevent auto-maximizing on browser start, and inform users that maximized windows are detrimental to privacy in this mode.
I used the workaround mentioned in this thread to fix the problem of not being able to add separators between buttons on the toolbar. Here's a pix of what they look like in customize mode:
However, Waterfox now resizes itself on opening and looks like you see it in the image. I don't know whether the spaces are the cause of it though.
My system is Windows 8.1 patched using security only updates every month rather than the rollups containing telemetry and other Microsoft bloatware just in case that's relevant.
The text was updated successfully, but these errors were encountered: