NoScript 10 unusable on second desktop (scaling applied)

Ask for help about NoScript, no registration needed to post
Carottinger
Posts: 1
Joined: Sat Dec 09, 2017 2:17 pm

NoScript 10 unusable on second desktop (scaling applied)

Post by Carottinger »

Next to my Win10x64 (1709) asus laptop I have a Full-HD monitor. As the laptop resolution of 3.2kx1.8k is way to high next to a FullHD (1.920x1.080) 22" monitir I reduced the laptop to 1600x900 (and increased the scaling to 125%) yielding similar sizes and mouse movements on both screens.
Once I move my (FF57) from the laptop to the monitor the NS (v 10.1.5.6) pulldown is croped to the upper left corner so I won't see see 30-40% of the site list. Sometimes the site names are barely visible.
In order to adjust the site blockings (way more complex as NS 5, far less to be configured in general, way more each particular site - why?) I have to my browser back to the laptop screen, do the adjustments and finally moving it back - quite anoying. Is NS 10 computing its sizing badly (It did not occur on NS 5)? On modern portals some 30% of all site are not even visible to adjust ...
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
User avatar
Giorgio Maone
Site Admin
Posts: 9454
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: NoScript 10 unusable on second desktop (scaling applied)

Post by Giorgio Maone »

It's a Firefox bug affecting all the extensions with a popup menu.
I've tried to implement the suggested work-around in one of the recent RCs, but it actually made the thing worse for people (arguably more than those with a second monitor at different density) who use any zoom factor on web content.
Let's hope Mozilla manages to fix it soon :(
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
User avatar
Giorgio Maone
Site Admin
Posts: 9454
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: NoScript 10 unusable on second desktop (scaling applied)

Post by Giorgio Maone »

And the good news, it's now fixed in Nightly and backported to 58, so the fix is going to be in next beta and release.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Post Reply