-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Texts are very blurry in many websites ( Youtube Notification Pannel ) #240
Comments
What is "Youtube Notification panel" ? |
Well it got fixed when I disabled Viewport Size Protection |
notification slide in youtube.com |
there should be no notifications, can you take a screen shot please? |
Texts in this panel was unclear and blurry before I turned off Viewport Size Protection from privacy>site settings>Viewport Size Protection |
@abznidre thanks! @PF4Public found a way to reproduce it! |
@abznidre did you install chrome or brave? |
@abznidre another thing, could you please show me WHERE that notification appears? i.e. could you please take a screen shot of the whole screen? of course blur anything you like. |
It is a little bell icon in the upper right corner of the page, near your account info. You need to be logged in, have any of your subscribed channels publish a video recently in order for notification to appear.
Hope you can fix it at last! |
No I am still using chromite |
yes its that little bell icon |
@uazo I found another related case of blurriness: network graph on GitHub Observe that |
No luck, I cannot reproduce it. |
can you tell me the resolutions of your screens? |
1920 . 1080. |
@leduyquang753 What is the dpi of your screen? |
142 DPI. |
@uazo I still think that it might be related to hidpi screens, do you have one for a test? |
142 DPI is same as me (see https://dpi.lv) |
I cannot reproduce any except this #240 (comment) which by the way is also detected by creepjs: |
some updates. first of all, I studied my patch, which I no longer remembered :) then, the problems of text blurring is unfortunately insurmountable. what the patch does is change the internal zoom of the dom elements, because the zoom factor is the value used to recalculate ALL the blink co-ordinates, and here the fact that the user is protected from fingerprinting scripts on the coordinates, which are ultimately based on screen geometry (at least in android). in relation to #240 (comment) this is exactly how it works, i.e. 100px is no longer 100px but a little more or less. can be exploited to recognise cromite, but not the user, and in any case, it would not be so different from bromite (and ungoogled chromium) where the coordinates were 'dirtied' at random. The only thing I would like to fix is to make it more difficult to tie the user/browser to the ip, but that's another story. in relation to #240 (comment) what creepjs detects is the difference between the co-ordinates of a known rectangle (i.e. 0-0x100px-100px rotated by 45 degrees) and those exposed by the browser, but it is more a mechanism for detecting a lie rather than obtaining any information for fingerpriting the device, probably serves to detect whether the user is using a 'normal' browser, more related to anti-fraud systems |
@PF4Public I found this by chance: https://www.reddit.com/r/Cromite/comments/190hge2/blurry_fonts_in_cromite_on_certain_sites_sharp_on/ do not install anything, but could you try adding via devtools this css?
can you also change the 0.1 to some value? thanks! |
I've added that to |
too bad. thanks for checking. |
Maybe I should give that extension a try? |
haha, you want my authorisation? only if on stamped paper :)
As you wish: I simply did not want to ask you to trust something that I do not know and that has no open code. |
Why did you consider
And only if it's notarized! :D
That's kind of you! There are plenty of technical means of handling unknown/untrusted software. |
no, I remind you that I don't have that problem (maybe I'm on the computer too much and don't realise it :)
not so far, I can't think of anything else. |
Sorry, I forgot this. simply because that user said he solved it that way |
Quote from extension description:
Perhaps this workaround works only on Windows? I tested on Linux. |
@tz-shuhag can you try? |
RGBA = Red, Green, Blue, A = Apha (Transparency in percentage, here min. 0 to max. 1), change from 0.1 to 1 For Reference :- |
Sorry to say no as I am also using linux at this moment. In windows I was easily able to overcome this problem by turning off Viewport Size Protection from settings>privacy>site settings>Viewport Size Protection. I would recommend you to just keep viewport size protection off by default and not go on that much on this issue. Android version of chromite is fantastic man. It's my default android go to browser. lastly do you @uazo have any plan to build something like chrome os or fyde os. I am quite interested in Chromite OS 😀. |
thank you @tz-shuhag I didn't think you were referring to linux.
no, but thanks.
too many things to do first, maybe in a few years. |
So, have you found a solution, is it fixable? |
let's say I found a way to reproduce and investigate the problem. claim to be able to solve it, not yet. |
for that specific situation the problem is opacity. values such as 0.999 lead to that effect: @PF4Public can you verify it? |
I can confirm that disabling opacity makes text go sharper. This does not fix the issue with canvas though as it is independent of opacity. |
thanks for the check.
It is not possible to solve this problem, it is inherent in the way the patch works. |
I understand BTW, could 8998e3d be used for fingerprinting? |
theoretically no, I checked. |
Preliminary checklist
Is your feature request related to privacy?
No
Is there a patch available for this feature somewhere?
Texts are very sharp and clear when I open the notification tray of yourtube in Chrome. So yeah its available in chrome and other chromium based browsers ( brave, edge, opera, ungoogled chromium )
Describe the solution you would like
For now just turn off Viewport Size Protection from settings>privacy>site settings>Viewport Size Protection. In future this might get fixed with some updates.
The text was updated successfully, but these errors were encountered: