I noticed recently that an old blog site of mine stopped loading its styles.css and so displayed see as a horrible mess. Nothing has changed on the site, just the browser.
The reason?
Today's browsers (ie anything #Chrome based) are becoming authoritarian about what they will display. This isn't a security issue, but an increasing stringency on something that makes no sense at all.
The solution?
Remove <!DOCTYPE> and pretend you're an old website, so they need to display as it was. 🤷♂️ 🤦♂️
A partire da oggi le estensioni di Chrome non saranno più le stesse. Manifest V3 inizia a fare sul serio
I permessi per le estensioni del browser passano definitivamente nelle mani di #ManifestV3. Per ora solo per gli utenti beta di #Chrome, ma nei prossimi mesi raggiungeranno tutti gli utenti
@edinbruh@informapirata@eticadigitale ciao la prima frase per Vivaldi è: "usa lo stesso motore di Google Chrome", se pensi però che ci possano essere altre frasi che possano lasciar intendere quanto dici dimmi pure quali cosi provo a vedere e a eventualmente riformulare il modo in cui sono scritte! Grazie intanto per i commenti, sono sempre benvenuti
This means, among other things, that uBlock Origin is about to be disabled in Chrome. Google will choose a different extension to recommend but it can not be as effective as #uBlock Origin.
Following #Google's example, may I instead recommend you switch to #Firefox.
Firefox will continue to support Manifest v2, and consequently uBlock Origin and other extensions that can not be implemented with Manifest v3.
@ku It doesn't have any impact on Vanadium. It uses the built-in filtering engine and doesn't support extensions. We plan to upgrade the built-in filtering engine to support what we want to provide, similar to Brave. Any other features will also be implemented ourselves rather than by having people run third party code with access to their data. Extensions don't follow the standard site isolation model so they're always a downgrade in that regard for privacy and security.
#Chrome friends,
I moved to a new Mac and found that Shift-Click in Chrome no longer worked. Turns out a fix is to turn off "Use Graphics Acceleration when available"!
But at what cost? I want graphics acceleration! I really need shift-click to work in text editing. What am I giving up?
And why in hell does graphics acceleration kill shift-click?
NB: Please don't tell me to not use Chrome. That's not my question.
Anyone here seen #Chrome extensions with #DevTools panels just not display sometimes?
I'm seeing some really weird behavior recently I can't explain and would appreciate if anyone has experienced the same problem and could validate my sanity:
Therefore: With #Chrome, you only get a secure #browser when you pay money to #Google. Otherwise, you get a crippled product that exposes you to risks.
Switch to a #Firefox browser in order to get a browser that offers maximum #security by default.
@publicvoit Nearly 2/3 of all browsers used worldwide are Chrome. You are right: It is a customer's choice, however it doesn't make their behavior any better, quite the opposite: they are aware of their dominance and therefore deliberately exploit it to undermine the right to privacy.
I've been using Firefox since the 90s and not using Chrome as my main browser ever. 😉
If Google manages to dominate the browser market >90%, Firefox will vanish and Google is able do dictate the whole web standard chain for their own purpose and profit. Basically the end of the WWW as we know it.
Plus de 97 000 sites web affichés dans le navigateur #Chrome analysés par des chercheurs de l'université de Zurich, en observant plus particulièrement les fenêtres de consentement pour les #cookies : 90 % de ces sites contiennent au moins une violation de la #ViePrivée (absence du bouton pour refuser, refus non pris en compte, dépôt de cookies avant l'interaction de l'utilisateur, consentement implicite) et 65 % ignorent les choix de l'utilisateur. #RGPD https://eupolicy.social/@ilumium/112235832500838592
via @ilumium
@alainmi11@NilsRenaud Aaaaactually, @noybhas "developed a mass scanning system to automatically detect unlawful cookie banners and create complaints which are sent to the companies, giving them a grace period to adjust their cookie banner before the complaint is submitted to the responsible authority."
I guess it's more a matter of those authorities actually doing something.
Oh, and, BTW, does anyone know what the crash dump logs browsers generate are actually used for? None of the teams involved in helping me troubleshoot my crashes seemed to be interested in them nor did they seem to have any idea what they would do with them. #crash#Chrome#Edge#Google#Microsoft
@darrell73 If you're talking about .dmp files, I'm really surprised that the browser teams don't want them. Even as a third party I think I would be able to make some sense of a .dmp file from Chrome by loading it in the WinDbg debugger, if I know what version of Chrome you're running.
@darrell73 Actually though, I'd think Vispero would be in the best position to debug, since they'd have access to both the Chrome PDB files (which I believe are public) and the private JAWS PDB files.