أبوعبدالعزيز00
New Member
Last edited:
[AdGuard for Windows] v6.2.432 RC
- Thread starter vasily_bagirov
- Start date
- Status
Purple Tentacle
Member
T
The Commissioner
Guest
In the words of Deadpool
Purple Tentacle
Member
New font looks fine. There seriously is no need to add an option.
Blaz, please, your reaction to pretty much any change of the interface during this beta has been: "I don't like it, give me an option to switch it back".
That's just not feasible. Not only would it be terrible UI and decrease usability (Schwartz calls this the "Paradox of Choice" and there are studies confirming that too much choice is quite detrimental to user interaction), it would also require far more code maintenance and slow down development in the long run.
Build 424 is running well ... I should have complained about the lack of updates sooner.
Blaz, please, your reaction to pretty much any change of the interface during this beta has been: "I don't like it, give me an option to switch it back".
That's just not feasible. Not only would it be terrible UI and decrease usability (Schwartz calls this the "Paradox of Choice" and there are studies confirming that too much choice is quite detrimental to user interaction), it would also require far more code maintenance and slow down development in the long run.
Build 424 is running well ... I should have complained about the lack of updates sooner.
Purple Tentacle
Member
If the font was changed to improve screen reader compatibility, then that was a darn good reason to change it. And the old filtering log was absolute not fine, it was highly unintuitive to new users. The new one still has major issues, but claiming that the old one was "fine" is absurd.
I'm not saying it is not a bad change (good for the blind people), but the user should have the choice if he wants to see that interface change or not rather than stuck being with an old version.
I just don't like forced changes for all users which are good only for a handful of people.
I just don't like forced changes for all users which are good only for a handful of people.
gustms
New Member
I really liked this new update. Testing the new improvements for the userscripts. New Popup blocker was an welcome addition. Thanks.
The new font looks great for me as well. In my opinion, interface customization features are not necessary in this type of software. It is not like we keep the UI open all the time.
The new font looks great for me as well. In my opinion, interface customization features are not necessary in this type of software. It is not like we keep the UI open all the time.
I do use filter editor/protocol a lot and this new Font is an eyesore for me.
NET::ERR_CERT_COMMON_NAME_INVALID when visiting the following site.
Possibly NSFW:
https://isexpro.net/korean19-com-porn-kp1602022.html
Anyone else can reproduce?
Possibly NSFW:
https://isexpro.net/korean19-com-porn-kp1602022.html
Anyone else can reproduce?
Attachments
Thanks for testing @Boo Berry . I could not disable Adguard completely to check.
Shouldn't Adguard not trying to i inject certificate to the site If it already contains an invalid certificate?
Shouldn't Adguard not trying to i inject certificate to the site If it already contains an invalid certificate?
Guys, I am sorry for the late reply.
First of all, regarding the new font, it is final. The problem with the previous font is that it covers only part of the letters (Latin + Cyrillic). It does not cover Latin Extended and a lot more so we anyway had Open Sans as a fallback. This, in turn, caused issues with the UI layout -- these fonts are rather different and we couldn't make it work for both. We struggled for a long time trying to make them work together and after all decided to use Open Sans only.
We may change it in future. For instance, I like Monserrat much more than Open Sans, but in order for all this to work, we will need to order a new font that will inherit Monserrat latin letters and extend it with Cyrillic and Greek letters.
First of all, regarding the new font, it is final. The problem with the previous font is that it covers only part of the letters (Latin + Cyrillic). It does not cover Latin Extended and a lot more so we anyway had Open Sans as a fallback. This, in turn, caused issues with the UI layout -- these fonts are rather different and we couldn't make it work for both. We struggled for a long time trying to make them work together and after all decided to use Open Sans only.
We may change it in future. For instance, I like Monserrat much more than Open Sans, but in order for all this to work, we will need to order a new font that will inherit Monserrat latin letters and extend it with Cyrillic and Greek letters.
The certificate is valid in this case, but it is used for a wrong website. AG does intercept HTTPS in this case because browser anyway can detect the CN mismatch and warn the user.
- Status