Waterfox: Dissenter Extension displays incorrectly on Windows 10 version

[tcreek]

So here is the Windows version.

And the Linux (Debian) so you can see the comparison

Since it is the same version of the extension, I am assuming it is Waterfox with the issue.

Both OSs are using version 56.2.12, and both using Dissenter version 0.1.10

[grahamperrin]

56.2.12 on Windows 10:

[tcreek]

Well, seems some are having issues. I have removed it, and installed again with same results.

[SenpaiSharp]

Do you have any other plugins that would be messing with the default zoom levels of web pages or altering their content in any other major way?

[tcreek]

No. I have the same one 3 ones on each browser.

TrackMeNot
TabMixPlus
Dissenter

[grahamperrin]

Reproducible with a new profile?

• about:profiles

Can you provide a full-screen shot? It might help to sort of read between the lines of the issue …

[tcreek]

I created a new profile, It is the same exact result.

[grahamperrin]

Thanks, is that full screen or a full window?

What resolution is the display?

[tcreek]

That is full screen @ 1920 x 1080

[grahamperrin]

Which version of Windows?

What's the hardware setup?

Windows scaling issues for high-DPI devices

Maybe report the issue to developers of the extension, https://github.com/gab-ai-inc/gab-dissenter-extension/issues

[tcreek]

Windows 10. It's a one year old laptop. I use the browser in an external monitor. Moving the browser to the main laptop screen, which is also 1920 x 1080, makes the extension appear correctly.

I will give them a try and see what they have to say

[grahamperrin]

… laptop … 1920 x 1080, …

What make and model is the laptop?

[tcreek]

HP Pavilion Laptop 15-CC5XX

[grahamperrin]

Does it have the 4K (3,840 x 2,160) IPS option?

[tcreek]

I am not sure about that, but it is capable of supporting an external 4k monitor.

[tcreek]

Here is a screen shot of FireFox 69.0.2 with Dissenter version 0.1.10 on the same screen as is Waterfox

[grahamperrin]

If you like, use mozregression to tell which build of Firefox was the last to be bugged in the same way as Waterfox Classic.

If that can be told, then it should become easier to pinpoint the Mozilla commit(s) from which a fix might apply to Waterfox Classic.

[tcreek]

Seems to me a Waterfox issue

[grahamperrin]

… with Waterfox primarily using code from Firefox; can you use mozregression?

[tcreek]

Yeah, that is what I tried. I attempted a bisection of version 55 and 56. It kept bringing up version 56

[grahamperrin]

55 and 56.

You'll probably find the bug reproducible with Firefox 56.0.2 (yes?) so instead, try a higher range.