[MPEG-OTSPEC] [EXTERNAL] questions on OT-SVG in Chrome, MS Edge and Firefox

[William_J_G Overington]

Hi
I refer to
https://lists.aau.at/pipermail/mpeg-otspec/2024-February/003285.html 
<https://lists.aau.at/pipermail/mpeg-otspec/2024-February/003285.html>
--
A discussion about the technique of using an SVG file exported from 
Affinity Designer (Affinity Designer not having colour font capability) 
to produce a colour display using Microsoft Edge has arisen.
https://forum.affinity.serif.com/index.php?/topic/199300-color-font-is-not-being-displayed-in-affinity-designer-2-desktop/&do=findComment&comment=1178254 
<https://forum.affinity.serif.com/index.php?/topic/199300-color-font-is-not-being-displayed-in-affinity-designer-2-desktop/&do=findComment&comment=1178254>
https://forum.affinity.serif.com/index.php?/topic/199300-color-font-is-not-being-displayed-in-affinity-designer-2-desktop/&do=findComment&comment=1178261
Is the issue in this thread related to that or is about something 
different please?
Best regards,
William Overington
Monday 26 February 2024
 
 
 
------ Original Message ------
From: mpeg-otspec at lists.aau.at
To: htl10 at users.sourceforge.net; mpeg-otspec at lists.aau.at; 
jfkthame at gmail.com
Sent: Tuesday, February 13th 2024, 00:44
Subject: Re: [MPEG-OTSPEC] [EXTERNAL] questions on OT-SVG in Chrome, MS 
Edge and Firefox
 
> Guess OT-SVG support was broken when MS Edge moved to a Chromium-based 
> backend in April 2021.
 
That’s correct.
 
 
Peter
 
From: Hin-Tak Leung <htl10 at users.sourceforge.net> 
Sent: Monday, February 12, 2024 3:07 PM
To: mpeg-otspec at lists.aau.at; Jonathan Kew <jfkthame at gmail.com>; Peter 
Constable <pconstable at microsoft.com>
Cc: suzuki toshiya <mpsuzuki at hiroshima-u.ac.jp>
Subject: [EXTERNAL] questions on OT-SVG in Chrome, MS Edge and Firefox
 
Hi,
I have continued to keep the blink/skia patches [1] up to date to 
current Chromium. And continue to test them [2] with QT WebEngine, which 
is a slimmed-down Chromium code variant up to about 3 months behind in 
latest Chromium development. Am trying to get the QT folks to take the 
patches [3].
Since some claimed that MS Edge supports OT-SVG back in 2017, and MS 
Edge has been available for Linux for a while, I gave it a try, and it 
is a NO. Guess OT-SVG support was broken when MS Edge moved to a 
Chromium-based backend in April 2021.
Anyway, here is a question for Peter and possibly also other Microsoft 
folks:
- I have no idea how much current MS Edge on windows differs from Chrome 
on windows, but would you pass the URL for the patches to the relevant 
people and let them see what they see fit to adapt please? Thanks. 
Feedbacks and corrections/modifications can go to [1]'s issues, etc or 
directly/privately to me if needed.
And here is a question for Jonathan, and possibly other Firefox folks:
- logically my chrome patches are in 3 parts, a one-liner switching 
OT-SVG support on in Skia, tell OTS to let such fonts pass-through as a 
usable font format, and get Blink to use freetype for non-OS-native font 
formats similar to sbix for windows etc. The 2nd part is somewhat common 
to Firefox - how does firefox deal with OT-SVG web-font sanitizing-wise? 
Does its copy of OTS (AFAIK) let them through and just hope the SVG 
processing is robust enough, or do some XML/etc validation on the way?
Would like to hear what Safari/Apple folks or webkitgtk folks (both of 
them supoprts OT-SVG, the latter I tested myself with webkitgtk-sharp) 
who like to comment on the sanitizing/security aspect of OT-SVG web 
fonts too. 
Hin-Tak

[1] https://github.com/HinTak/chromium-mod-CI 
<https://github.com/HinTak/chromium-mod-CI>
[2] https://github.com/HinTak/Qt6WE-OT-SVG 
<https://github.com/HinTak/Qt6WE-OT-SVG>
[3] https://bugreports.qt.io/browse/QTBUG-120543 
<https://bugreports.qt.io/browse/QTBUG-120543>

_______________________________________________
mpeg-otspec mailing list
mpeg-otspec at lists.aau.at
https://lists.aau.at/mailman/listinfo/mpeg-otspec 
<https://lists.aau.at/mailman/listinfo/mpeg-otspec>
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20240226/81f1f194/attachment.htm>