Do we have any sense for when (if?) the View Transitions API for cross-page animations will be unflagged as experimental, and just a default part of the browser?
It's nice to have it to play around with now, behind a flag, but it also kinda sucks to know literally nobody but web devs are ever going to see those transitions (because normal users don't go edit their Chrome flags). #webDev#chrome#browsers#css
Chrome has started doing this thing where a tab seems to "drop" its contents - it's noted by a little circle with dotted lines on one half. When I click back to the tab, the page then needs to reload.
I assume that it to keep overall memory down, but I find I can't toggle back and forth between references nearly as quickly anymore. Does anyone know if that is a setting I can change somewhere?
This great news out of Australia (via @owa) makes worldwide browser choice more likely. Every jurisdiction that rejects Apple and Google's underhanded browser nonsense bring us a step closer to ending App Store rent extraction and proprietary lock-in.
The W3C, founded in 1994 by web inventor Tim Berners-Lee, has quit X and declared the fediverse to be their primary social media channel. Follow them at: @w3c
@f09fa681 Issue #552 of whatwg/html pretty much explains for itself what it means for contributions which don't get "enough implementer interest" in the #WHATWG despite having a significant #webdev grassroots support.
This obsession in making sure at least two "implementers" have the feature baked into their codebases is frankly bull and is one of the factors of why we have such a #Google-biased #web. Theoretically it's there so that every feature would be certain that there are players backing and seeing that feature being useful and good for the #openweb, but in reality it has become Google's veto in most cases, with the popular being one of the victims here. It has been a standard for quite some years, yet Chrome's developers seem to have an extreme case of "Not Invented Here" syndrome and decided not to implement it for whatever reason. Maybe they really don't have an interest in it and are therefore in "patches welcome" mode like a corporation would do in #opensource. Or maybe, they saw it as a threat to their Google #WebComponents because it pretty much satisfies most of the usecases their toy project #ShadowDOM is designed to solve, and web developers don't want to deal with such a complex feature just to limit the scope of their #CSS. Whatever the reason is, this should not kill a feature that has been long-awaited by many web developers to be supported in their #browsers and is backed by a well-maintained and developed #browser (which is #PaleMoon in this case).
Allowing comments in GitHub issues is ultimately useless if the final decisions are made by a closed cabal of big "implementers" who as history has shown has been pretty much Google's lapdogs most of the time.
Hey, remember how browsers used to randomly take you back to the previous page while you were trying to delete text, because both actions used the same key?
Applescript support in #ArcBrowser is pretty broken. One space, one window, three tabs open, but via Applescript it reports a list of 57 (!) dysfunctional Tab objects.
Well, my code-level support ticket was picked up by Apple, and I think I have my answer — it looks like I'll have to sell my upcoming app Browser Actions outside the App Store after all.
Do you have a #cyberdeck for daily use?
Any cool gadgets or #techwear?
Souped up terminal prompt beyond oh-my-zsh?
Any other useful desktop apps which help you trough the day?
All the RGB you can fit into your room?
Preaching the gospel of #Arch Linux?
I kinda feel pretty un-cyber these days and was wondering…
The remaining problems are generally #browsers that haven't implemented #SSL/#TLS correctly, mishandling it when a visited URL includes the trailing dot. It sounds like #Safari - maybe only on #IOS? - is one of those. They report an invalid #certificate because the #URL of the page includes a trailing dot on the domain, while the CN in the cert doesn't have it (as those are always absolute).
#browsers#privacy#uBlockOrigin#google#startpage
Quel moteur de recherche utilisez vous ?
google ?
hum j'utilise startpage.com
Pourquoi ?
avec l'extension uBlockOrigin installé, constaté les différences juste en allant sur la page d'accueil www.google.com et sur startpage.com
Concerning #browsers and #manifestv3, here's your reminder that Mozilla aren't saints either, and they have been in some deep shady shit for the past handful of years.
This of course doesn't discredit any issues other browsers may have. Just do your research with credible sources, use the browser that best suits you, and don't fall into the trap of the Firefox cult which loves to ignore and downplay the problems surrounding Mozilla.
I switched from Mosaic to Netscape Navigator to Firefox.
I never really liked Internet Explorer or Opera or Safari or Chrome.
I did use Pale Moon for a while, mainly because I thought a 32bit browser on a 64bit operating system did not make sense. And I liked Konqueror for a while as the 'browser without history', but that is what a 'private window' is for these days.
I also remember minuet for use on the terminal, later I used Lynx and Links for that. Now I never use text-based #browsers
You know you are a #frontend#developer when you have way too many #browsers (all with different themes you can you tell what is what) just so you test things from multiple accounts simulatneously...
Anyone found a better soution to this little game?
Restarting your apps while the network is offline makes you realize some things are silly… like needing to click the Reload button in #web#browsers' error pages, when they very well know when the operating system is fully back online anyway.
Therefore, I filed a request for #GNOMEWeb / #Epiphany to do that for me when #GNOME / #NetworkManager signals that online connectivity has been restored: https://gitlab.gnome.org/GNOME/epiphany/-/issues/2230
Apple loses on Appeal, CMA can restart investigation into browsers - Open Web Advocacy (open-web-advocacy.org)