The DnD Sanctuary

Pings => Otter Browser Forum => Topic started by: Emdek on 2017-11-01, 19:44:11

Title: (Pre) RC 2 release (01.11.2017)
Post by: Emdek on 2017-11-01, 19:44:11

Please note, we haven't entered feature freeze phase yet, so 1.0 will see some more stuff, not just fixes and updates.
Next stop, (Pre) RC 3, next month.
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: ersi on 2017-11-01, 20:03:24
/me goes to update
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Emdek on 2017-11-01, 20:04:29
Note that binaries will be available tomorrow, but source package and tag are already available.
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Mike on 2017-11-03, 08:40:29
The link for xp is incorrect.
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Emdek on 2017-11-03, 08:42:14
@Mike, fixed, thanks.
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: ovas on 2017-11-03, 12:10:33
The default zoom is very large in RC 2 release and v200
Win 64 font 150% on PC
Returned on v199
(https://picusha.net/img/2017-11/03/feoxy5vrp5sutm9yn0j13m5di.png)

Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Emdek on 2017-11-03, 13:09:24
@ovas, are you using HiDPI screen?
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Frenzie on 2017-11-03, 14:17:38
The default zoom is very large in RC 2 release and v200
Win 64 font 150% on PC
Returned on v199
An expected side effect of #1428 (https://github.com/OtterBrowser/otter-browser/pull/1428). Note that you most likely manually set "default zoom" to some larger value in Preferences → Content → Zoom previously.

You could also try to "disable DPI scaling" in the shortcut properties.

Combined with a 100% zoom level on a website, does the program correctly scale to ~150% or does it go overboard to, for example, 200%?
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: ovas on 2017-11-03, 14:41:54
I use this scale.
In v199 and others such a problem was not.

Spoiler (click to show/hide)
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Frenzie on 2017-11-03, 17:31:45
Right, but you presumably would've set the default webpage zoom to something higher than 100%. The difference is that in this case "100%" has taken on a slightly different meaning. The big question is whether at scaled 100% it's roughly correct (i.e., previous 150%) or basically wrong (e.g., previous 200%).
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: ovas on 2017-11-05, 16:33:11
Is there a solution to this problem?
In earlier versions, this was not.
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Emdek on 2017-11-05, 16:39:41
@ovas, AFAIK you can set environment variable to disable it, or wait for weekly 201 (Monday or Tuesday).
Title: Re: (Pre) RC 2 release (01.11.2017)
Post by: Frenzie on 2017-11-05, 17:18:58
Yes, on Windows you can use this to trigger the weekly 200/RC2 behavior on any Otter build:

Code: [Select]
set QT_AUTO_SCREEN_SCALE_FACTOR=1
otter-browser

And like this for the reverse:

Code: [Select]
set QT_AUTO_SCREEN_SCALE_FACTOR=0
otter-browser

It might be possible to string it together in a shortcut without having to create a batch file or open a command prompt, but my CMD syntax knowledge is a little rusty. This might not work as written:

Code: [Select]
set QT_AUTO_SCREEN_SCALE_FACTOR=0 & otter-browser

Another option would be something like this. This might not work as written either:

Code: [Select]
cmd /c "set QT_AUTO_SCREEN_SCALE_FACTOR=0&&otter-browser"