If it says there are any, just click the UpdateThere's been a lot of discussion recently about how "Safari is the new IE" ( 1, 2, 3, 4, 5).Google Chrome is also a very fast browser on all devices, but especially so on desktop. The page will automatically Check for Update. You will then be redirected to a page that shows you information about your browser. Find the Help button near the end of the list and click About Google Chrome. Open your Google Chrome Navigate to the three vertical dots in the top-right corner of the browser.You either have to wait for whole hours or simply kill the page and do your work all over again.Searchmine.net or simply called Search Mine is a malicious search tool that affects Google Chrome, Mozilla Firefox, and Safari browsers. Seeing Chrome page unresponsive errors is a pain. This is because there is too much workload in your browser.Refusing to engage with the contentious API proposals for real use cases doesn't actually protect the web anyway - it just pushes web developers and users into the arms of Chromium.We'll dig into each of these points in more detail in a second, and then we'll talk about what Safari could do instead.There have been other arguments made too, including much speculation about why Safari might be killing the web - is this motivated by protecting Apple's app store profits? I'm going to ignore those suggestions entirely, and stick to concrete problems. The largest Safari complaint is unrelated to experimental features from the Chrome team: it's the showstopping bugs in implemented features, made worse by Safari's slow release cycle. Most features that Safari hasn't implemented have no hint of security, privacy or performance concerns, and they've been implemented in every other browser already. Re: Issue 165575 in chromium: kiosk screensaver always in magnifier mode Re: Issue 165569 in.That is worth further discussion, because it's widespread, and wrong.More specifically, Safari's approach isn't protecting the web from bloat & evil Google influence, because: Load html page in Chrome kiosk mode (not full-screen).Hurt battery life, by making web pages bloated & inefficientThis isn't true. Risk security, by increasing the browser attack surface Reduce user privacy, by supporting tracking Unfortunately though, today there are big problems, and the current trajectory is making the web worse, not better.Of the three points above, I think the final one will be most interesting and contentious, but let's get the first two cleared up first: Safari is killing the web by omitting easy safe featuresA frequent argument made is that the features which Safari does not implement all either: That does not mean their current approach deserves our blind support.I'm sure the Safari team are working on the issues below already, and I think it's likely that the problems fundamentally derive from management decisions about company priorities rather than the team themselves.
![]() :focus-visible, which avoids accessibility/design conflicts by showing focus styling only during keyboard navigation. Implemented in Firefox in 2012 and Chrome in 2013. Resolution media queries, which allow content to be styled to match the device pixel density. ![]() Implemented in Firefox in 2015 and Chrome in 2017. scrollIntoView() to scroll to an item on the page. Implemented in Chrome in 2017 and Firefox in 2020. Regex lookbehind in JavaScript. Implemented in IE 6 (!!!) in 2001, Firefox in 2011 and Chrome in 2018. Game boy mac emulatorThere's been no specific public objections from the Safari team on any of these that I can see, only silence.As far as I'm aware, there's also no signal from the Safari team that any of these are coming any time soon, and I've omitted quite a few more missing features that are implemented, but behind flags (often for years) but which are presumably going live sometime soon.According to Can I Use's metrics, Safari is lacking about 10% behind Firefox and 15% behind Chrome in feature support. Implemented in Chrome in 2018 and Firefox in 2019.Each of these has a published standard and is implemented by multiple browser engines, including Firefox, with no concerns I can see anywhere. AV1 video and AVIF images, a new efficient and freely licensed compression format. Implemented in Chrome in 2014 and Firefox in 2016. Bumil safe esd 101 manualService Workers, for page request middleware (offline support & caching) - released 2 years after it was supported everywhere else Date and time input types - released 4 years after Firefox and 9 years after Chrome If there was a good argument against these features, they should clearly never have been implemented.There's no good case for implementing web platform features but just many years after everybody else, such as: Safari is not doing well:The " they're only ignoring bad features" argument is made weaker by Safari's previous behaviour with such missing features, where many have eventually been implemented without objection, but years behind other browsers. Safari is slowing that down progress here.Ignoring standards like this does not help the web evolve more cautiously - once these features have been stable for years in every other browser they can't be changed anyway. They're also not shiny irrelevant features that "bloat the web" in any sense: each example I've included above primarily improving core webpage UX and performance. This adds delays easy real-world use of otherwise standardized features shipped by every browser for an extra year or two (on top of the existing time for standardization & implementation) if it's ever implemented at all.Again: these are not contentious features shipping by only Chrome, they're features with wide support and no clear objections, but Safari is still not shipping them until years later. Safari is killing the web through show-stopping bugsIn addition to missing features, Safari has a lot of bugs in its implemented features of various web standards. It's exceedingly rare now to see a web feature primarily driven by Apple. In the past (the early 2010s) Apple was frequently leading the way on new features, as the very first browser to ship major JavaScript APIs like Web Workers, and the browser driving experimental prefixed features like CSS Canvas backgrounds.
0 Comments
Leave a Reply. |
AuthorMike ArchivesCategories |