Why can't built-in browser (like in Google Chrome and Firefox) password managers can't handle exact URLs? There is nothing worse than password manager that tries to fill your password in wrong fields.
Keepass HTTP connector which I've been using also can do it, but browser extensions for that has gone unmaintained. I'm planning to write my own, but it's one of those chore tasks I'd rather not.
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
In case you’ve been asleep at the wheel – and if you’re still using Chrome, you most likely are – Manifest V3 will heavily limit what content blockers can do, making them less effective at things like blocking ads.
Einen Beitrag zum Thema Browser zu veröffentlichen, ist mindestens genauso anstrengend wie zum Thema Messenger. Inhaltlich setzt man sich kaum mit den Aussagen und Erklärungen auseinander, sondern Stammtischparolen ersetzen dann eine ernsthafte Diskussion. Auf diesem Niveau möchte ich wirklich nicht diskutieren.
Most Web-savvy folks know that Chrome’s lineage can be traced back to Safari (WebKit, etc.), and be traced further back to KDE’s Konquerer (KHTML, etc.).
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.
Oho, za chwilę przywrócą tę funkcję do Firefoksa, bo oni kopiują Chrome w głupi sposób, więc i skopiują rzecz, którą wcześniej już mieli i usunęli, bo chcieli skopiować sztywność menu z Chrome... xD #firefox#chrome#mozilla#google#browser
@ehrba My answer not as a #GIS professional but enthusiast and long time #Linux user: Any distro you feel comfortable with. If you're expecting the latest releases, try some rolling release. Otherwise, my usual suggestion, #Ubuntu, has been misbehaving a little with #snap (#chrome sometimes not being able to launch or access user's files because of a technical issue), so probably not that. I'm a #Debian user, so my personal suggestion is Debian stable or testing.
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.