Skip to main content
Topic: (Pre) RC 2 release (01.11.2017)  (Read 5468 times)

(Pre) RC 2 release (01.11.2017)

  • improved support for styling tab bar text;
  • added support for deleting User Scripts in Addons Manager;
  • restored inline URLs completion;
  • added action for peeking tab contents;
  • multiple bug fixes and stability improvements.

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.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

Re: (Pre) RC 2 release (01.11.2017)

Reply #1
 ersi goes to update

Re: (Pre) RC 2 release (01.11.2017)

Reply #2
Note that binaries will be available tomorrow, but source package and tag are already available.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

Re: (Pre) RC 2 release (01.11.2017)

Reply #3
The link for xp is incorrect.

Re: (Pre) RC 2 release (01.11.2017)

Reply #4
@Mike, fixed, thanks.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

Re: (Pre) RC 2 release (01.11.2017)

Reply #5
The default zoom is very large in RC 2 release and v200
Win 64 font 150% on PC
Returned on v199



 

Re: (Pre) RC 2 release (01.11.2017)

Reply #6
@ovas, are you using HiDPI screen?
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

Re: (Pre) RC 2 release (01.11.2017)

Reply #7
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. 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%?

Re: (Pre) RC 2 release (01.11.2017)

Reply #8
I use this scale.
In v199 and others such a problem was not.

Spoiler (click to show/hide)

Re: (Pre) RC 2 release (01.11.2017)

Reply #9
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%).

Re: (Pre) RC 2 release (01.11.2017)

Reply #10
Is there a solution to this problem?
In earlier versions, this was not.

Re: (Pre) RC 2 release (01.11.2017)

Reply #11
@ovas, AFAIK you can set environment variable to disable it, or wait for weekly 201 (Monday or Tuesday).
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

Re: (Pre) RC 2 release (01.11.2017)

Reply #12
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"