4 ms·

WebKit in Safari 26 beta

4 points by alwillis 1y ago

alwillis 1y ago
From https://front-end.social/@jensimmons/114654858122597718 https://front-end.social/@jensimmons/114654858122597718 * SVG icons * Every site can be a web app (special tech not required) HDR Images * <model> on visionOS * Immersive video and audio on visionOS * WebGPU * Anchor Positioning * Scroll-driven Animations * Pretty text * Contrast Color * Digital Credentials API * Trusted Types
ksec 1y ago
Out of all the listed features, I thought the most important one was "Website Compatibility". After 5 years since they picked up the pace of development Safari is still behind Firefox and Chrome. And every single release is a long list of fix but every now and then it is still safari the runs into issues. Hopefully "Website Compatibility" will leverage a lot of users on Mac platform to push webkit forward. Another disappointing thing is again not much mention on new Safari, non-webkit related features. Safari is the most memory inefficient browser out of the three. Especially in multi tab usage with no Tab Sleep / unload feature by default on macOS. Show Tab Overview still loads all Tabs with swap to kill your SSD. No List of Tabs view which is available on both Firefox and Chrome.
- alwillis 1y ago
  > After 5 years since they picked up the pace of development Safari is still behind Firefox and Chrome. According to Interop 2024, Safari is right there with Firefox and Chrome: https://wpt.fyi/interop-2024?stable https://wpt.fyi/interop-2024?stable Feature that Safari shipped before Firefox and Chrome [1] Features that were missing from Firefox that Safari has shipped as of 2½ weeks ago [2] Show all tabs [3] [1]: https://news.ycombinator.com/item?id=44074789 https://news.ycombinator.com/item?id=44074789 [2]: https://news.ycombinator.com/item?id=44067706 https://news.ycombinator.com/item?id=44067706 [3]: https://apple.stackexchange.com/a/206451 https://apple.stackexchange.com/a/206451
  - ksec 1y ago
    >According to Interop 2024, On paper yes. And that is after all these improvements. It still have more issues than others. >Feature that Safari shipped before Firefox and Chrome [1] Yes. I know all of them. But doesn't mean compatibility is close to perfect. And I am being specific about working in both browser and not just Chrome. Although Safari 18 is the one that has less issues so far. May be Safari 26 will reach the point where it is good enough compatibility wise. May be that is also what Apple feels that is why they have web compatibility button. >Show all tabs [3] That is Tab Overview and not a List of Tabs. Tab Overview will reload all tabs which means if you have hundreds if not thousands like some Firefox user, it would create paging issues and kill your SSD.
    - alwillis 1y ago
      > On paper yes. And that is after all these improvements. It still have more issues than others. Each browser has to pass thousands of the same tests; this isn't just "on paper" compatibility. Each browser is 100% compatible with the CSS Nesting (for example) specification and with each other. The browser vendors get how important it is for features to function and render the same way in each browser.

4 points by alwillis 1y ago

From https://front-end.social/@jensimmons/114654858122597718 https://front-end.social/@jensimmons/114654858122597718 * SVG icons * Every site can be a web app (special tech not required) HDR Images * <model> on visionOS * Immersive video and audio on visionOS * WebGPU * Anchor Positioning * Scroll-driven Animations * Pretty text * Contrast Color * Digital Credentials API * Trusted Types

ksec 1y ago

Out of all the listed features, I thought the most important one was "Website Compatibility". After 5 years since they picked up the pace of development Safari is still behind Firefox and Chrome. And every single release is a long list of fix but every now and then it is still safari the runs into issues. Hopefully "Website Compatibility" will leverage a lot of users on Mac platform to push webkit forward. Another disappointing thing is again not much mention on new Safari, non-webkit related features. Safari is the most memory inefficient browser out of the three. Especially in multi tab usage with no Tab Sleep / unload feature by default on macOS. Show Tab Overview still loads all Tabs with swap to kill your SSD. No List of Tabs view which is available on both Firefox and Chrome.

alwillis 1y ago
> After 5 years since they picked up the pace of development Safari is still behind Firefox and Chrome. According to Interop 2024, Safari is right there with Firefox and Chrome: https://wpt.fyi/interop-2024?stable https://wpt.fyi/interop-2024?stable Feature that Safari shipped before Firefox and Chrome [1] Features that were missing from Firefox that Safari has shipped as of 2½ weeks ago [2] Show all tabs [3] [1]: https://news.ycombinator.com/item?id=44074789 https://news.ycombinator.com/item?id=44074789 [2]: https://news.ycombinator.com/item?id=44067706 https://news.ycombinator.com/item?id=44067706 [3]: https://apple.stackexchange.com/a/206451 https://apple.stackexchange.com/a/206451
- ksec 1y ago
  >According to Interop 2024, On paper yes. And that is after all these improvements. It still have more issues than others. >Feature that Safari shipped before Firefox and Chrome [1] Yes. I know all of them. But doesn't mean compatibility is close to perfect. And I am being specific about working in both browser and not just Chrome. Although Safari 18 is the one that has less issues so far. May be Safari 26 will reach the point where it is good enough compatibility wise. May be that is also what Apple feels that is why they have web compatibility button. >Show all tabs [3] That is Tab Overview and not a List of Tabs. Tab Overview will reload all tabs which means if you have hundreds if not thousands like some Firefox user, it would create paging issues and kill your SSD.
  - alwillis 1y ago
    > On paper yes. And that is after all these improvements. It still have more issues than others. Each browser has to pass thousands of the same tests; this isn't just "on paper" compatibility. Each browser is 100% compatible with the CSS Nesting (for example) specification and with each other. The browser vendors get how important it is for features to function and render the same way in each browser.