Meeting minutes
Should SVG's <script> element support the fetchpriority attribute analogous to HTML's <script> element?
karlcow: implemented in Firefox and a not-merged patch in WebKit. Not implemented in Chrome.
karlcow: Is Chrome interested? Not part of the SVG spec right now.
Vinay: Async is in Chrome but not fetchpriority.
Vinay: I have to get back since the involved team has issues with the XML parser. But async ships.
ACTION: Vinay to investigate if this is in th einterest of Chrome to have fetchpriority attribute on SVG script element
Editorial] Convert main specification to bikeshed
karlcow: Will make more progress next week.
karlcow: I hope to finalize by EOY
[Editorial] missing word attribute in 6.1 section about styling.
karlcow: Minor: There is a sentence in the spec with a missing work about the style attribute. Should we add it?
krit_: Suggestion is to make the text formative, add a MUST and the word attribute. Only the information about SVG 1.1's behavior stays informative? I agree to your change suggest.
Vinay: me too
RESOLUTION: A the word attribute, make the text formative with a MUST. Follow the change suggestion from Karl on the ticket
[WPT maintenance] fixing xlink:href in tests
karlcow: There are a lot of usages of xlink:href in the spec. Should we replace it everywhere?
krit_: Are you confident that all browsers and editors support the href w/o prefix?
nzimmermann: How would we know which applications support SVG in general. Do we have a list?
krit_: SVG is widely used as interchange format on clipboard for various applications from InkScape to Illjustrator and borwser apps. Each app may have their own implementation with the own parser. I am not confident that they all support hred. Illustrator doesn't for example.
nzimmermann: We can deprecate it, but in the ticket Karl says something about the precedence which one to use href / xlink:href.
nzimmermann: wait, it is in the spec but not being tested
karlcow: it is in the spec and yes, Chrome team added a test
<krit_> s/no test/Chrome team added a test/
karlcow: question here is: Do we remove it?
nzimmermann: there could be a meta test for href and xlink:href
krit_: Do all browsers at least support href? Then we would have 3 implementatinos?
karlcow: yes, green everywhere with a few minor bugs in WebKit
caribou: and do we know about editor applications?
karlcow: the class of applications woul need to implement href AND use WPT
karlcow: We could decide to make href a prefix of xlink:href. But this is not the point for WPT.
nzimmermann: WPT is WEB platform. So we should remove the Xlink prefix where possible.
nzimmermann: good to get this off and align HTML and SVG more.
nzimmermann: IMO this only affects browsers. In reality, most other applications would not even use WPT.
Vinay: We will just have breaking tests that no one will fix.
ydaniv: In favor of removing it but did see XML based parser implementagtions of SVG which had the issue.
RESOLUTION: Remove xlink: prefix on href in all WPT tests w/ exception of the meta test to verify behavior on xlink:href to href
[WPT] Testing deprecated xlink:href and precedence of href #1043
karlcow: Chrome team submitted a test to test precedence of href to xlink:href. So issue is fixed.
nzimmermann: did you review it?
karlcow: I will double check
Next meeting
krit_: Next meeting on Jan 8.
charter: https://
<karlcow> RRSAgent: make minutes