5 ms·

Unfortunately there is no support for COLRv1 fonts on Safari (desktop or mobile).[0] There is support for COLRv0, so hopefully this will come to Safari/Webkit a

by s1mon 4y ago

Unfortunately there is no support for COLRv1 fonts on Safari (desktop or mobile).[0] There is support for COLRv0, so hopefully this will come to Safari/Webkit at some point.[1] [0] https://www.lambdatest.com/web-technologies/colr-v1 https://www.lambdatest.com/web-technologies/colr-v1 [1] https://www.lambdatest.com/web-technologies/colr https://www.lambdatest.com/web-technologies/colr

onion2k 4y ago
Unfortunately there is no support for COLRv1 fonts on Safari (desktop or mobile). The expectation that every user get's exactly the same experience regardless of what browser they're using has held the development of great user experiences on the web back for about two decades now. There's no reason why you shouldn't deliver a better experience for some users if their browser is more capable. Design a working minimal app. It'll probably be close to a plain HTML and CSS site that's rendered on a server. Then add in things that make it nicer to use while checking that the browser supports that feature so you don't break anything if it doesn't. Build up to a really nice experience. Progressively enhance the usr experience. This is literally how websites were built 20 years ago, but then developers got lazy and only wrote apps for the lowest common denominator, which meant any new features in browsers rarely good used, and at the same time slightly unusual browsers like Lynx got abandoned entirely. It really annoys me.
- wdb 4y ago
  Or Chrome shouldn't force a new colour font standard, they keep doing it, they could at least make sure creative tools has support for it.
  - account42 4y ago
    Exactly, at this point this should be a proposal for standardization with any implementations in browsers gatet behind flags, not something that google is shipping to end users on a whim.
  - onion2k 4y ago
    The beauty of what I suggested is that it stops anyone forcing a new standard for something. If a browser vendor creates a new feature then it's up to developers to support it. If they choose not to that's fine. If developers were happy to pick and choose which features to support, and were willing to put in the effort to support different approaches, then Google wouldn't have any power to force change across the whole web. They'd just make something that only works in Chrome, and developers would choose to use it or not.
alwillis 4y ago
WebKit’s position: https://lists.webkit.org/pipermail/webkit-dev/2021-March/031765.html https://lists.webkit.org/pipermail/webkit-dev/2021-March/031...
- davelab6 4y ago
  I wonder if that position will change as the utility becomes widely adopted.
gernb 4y ago
I'm confused as the examples seem to work in Safari For example this page works fine in Safari https://fonts.google.com/specimen/Nabla https://fonts.google.com/specimen/Nabla Both MacOS and iOS.
- davelab6 4y ago
  Google Fonts serves SVG-in-OpenType to legacy pre-COLRv1 browsers that support that older format, but you lose the variable fonts aspects.
  - account42 4y ago
    To non-Google browsers, not "legacy" browsers.

by s1mon 4y ago

onion2k 4y ago

Unfortunately there is no support for COLRv1 fonts on Safari (desktop or mobile). The expectation that every user get's exactly the same experience regardless of what browser they're using has held the development of great user experiences on the web back for about two decades now. There's no reason why you shouldn't deliver a better experience for some users if their browser is more capable. Design a working minimal app. It'll probably be close to a plain HTML and CSS site that's rendered on a server. Then add in things that make it nicer to use while checking that the browser supports that feature so you don't break anything if it doesn't. Build up to a really nice experience. Progressively enhance the usr experience. This is literally how websites were built 20 years ago, but then developers got lazy and only wrote apps for the lowest common denominator, which meant any new features in browsers rarely good used, and at the same time slightly unusual browsers like Lynx got abandoned entirely. It really annoys me.

wdb 4y ago
Or Chrome shouldn't force a new colour font standard, they keep doing it, they could at least make sure creative tools has support for it.
- account42 4y ago
  Exactly, at this point this should be a proposal for standardization with any implementations in browsers gatet behind flags, not something that google is shipping to end users on a whim.
- onion2k 4y ago
  The beauty of what I suggested is that it stops anyone forcing a new standard for something. If a browser vendor creates a new feature then it's up to developers to support it. If they choose not to that's fine. If developers were happy to pick and choose which features to support, and were willing to put in the effort to support different approaches, then Google wouldn't have any power to force change across the whole web. They'd just make something that only works in Chrome, and developers would choose to use it or not.

alwillis 4y ago

WebKit’s position: https://lists.webkit.org/pipermail/webkit-dev/2021-March/031765.html https://lists.webkit.org/pipermail/webkit-dev/2021-March/031...

davelab6 4y ago
I wonder if that position will change as the utility becomes widely adopted.

gernb 4y ago

I'm confused as the examples seem to work in Safari For example this page works fine in Safari https://fonts.google.com/specimen/Nabla https://fonts.google.com/specimen/Nabla Both MacOS and iOS.

davelab6 4y ago
Google Fonts serves SVG-in-OpenType to legacy pre-COLRv1 browsers that support that older format, but you lose the variable fonts aspects.
- account42 4y ago
  To non-Google browsers, not "legacy" browsers.