Chrome / TalkBack bug I first reported in 2020, and which was fixed for a time (?) appears to be back. Looking for confirmation before I file yet another one.
A named region with a tabindex does not expose its contents. Chrome / TalkBack only announces its accName and role.
I think I have an ugly workaround (“Shawarma” heading).
As expected, the Chromium intake person was unable to reproduce the issue (it may have been kit this time?), so I got 5 people to confirm and added a video: https://issues.chromium.org/issues/342172183
I really do hate how hard it is just to get a bug to get taken up.
Privacy matters! But what if the tools meant to protect us are being misused? Our latest study (to appear ARES '24) reveals surprising facts about HTTP Client Hints (HTTP CHs) on the Web. [THREAD]
The search for a slim, fast and modern browser might have come to an end. Ungoogled-chromium feels just like what I want. Even better than Vivaldi. But the setup process is a bit more nerdy.
Welcher Internet Browser ist "sicherer"?
Gute Frage und nicht simpel zu beantworten, doch nach meiner Auffassung ist es Firefox und weniger der sehr beliebte Chrome Browser.
So viel ich weiss, gibt es den Firefox länger und hat doch (knapp) weniger bekannte, so wie meistens behobene Schwachpunkte. Weshalb glauben so viele lehre Versprechungen von Konzerne?
Chromium update fixes 5th zero-day exploit for 2024
In Google's release notes for the latest Chromium 124.0.6367.201 source code it is mentioned that this release fixes a zero-day vulnerability. Beware: this is already the 5th zero-day which was reported and fixed in Chromium in 2024.
This vulnerability is already actively exploited in the wi
You cannot visit a #LinkedIn page from a #Chrome browser without LinkedIn creating an account based on the #Google account info that you're logged in with on that Chrome browser, even if you cancel the account creation process that LinkedIn automatically starts.
Because you didn't actually create that account, you cannot delete it. You have to complete the signup process just so you can then proceed to delete it.
Does no one at #microsoft challenge this kind of implementation?
@boo_@andros I didn’t foresee anyone turning Google’s #Chrome browser #JavaScript engine V8 (2008) into the server (#NodeJs, 2009) and desktop (#ElectronJs, 2013) runtimes that ate the world, but here we are.
And Electron was originally developed for #GitHub’s #Atom text editor (2008) before they were acquired by #Microsoft in 2018, subsequently discontinued in favor of #VSCode in 2022.
Don’t tell me what you can’t see happening if you don’t remember what already did