<krit> https://www.w3.org/TR/SVG11/
<krit> https://www.w3.org/TR/SVG/
Dirk: With the new publication of SVG2 CR, the short link is pointing to the SVG2 CR version.
<scribe> scribe: Amelia
Amelia: One problem is that this now creates 404 errors for chapters that no longer exist in SVG 2.
Dirk: We do eventually want to
redirect the short link to SVG 2, not sure if we're ready
yet.
... Wanted some feedback before I discuss with PLH.
Tav: Ideally, non-existing pages should include a note & redirect.
Amelia: First question is should these links be pointing to SVG2 at all. We were told that it is standard that once a CR is published, it becomes the "latest" version that short links point to.
Dirk: That's what W3C is used to, but with SVG it hasn't be updated in a long time, so a little bit confusing.
Amelia: Another issue is that we are a little messier than a CR should be. But I still think we should be encouraging people to look at the latest spec (and file bugs if there are problems).
Dirk, Tav: Agree.
Amelia: Next issue is those 404s.
Dirk: Not sure if we can fix them.
Amelia: We may be able to add stub pages in to our build that just have a short sentence indicating where the content has gone.
https://svgwg.org/svg2-draft/changes.html
Dirk: But would that not then integrate them into the single-page version of the spec?
Amelia: not sure.
Dirk: how many chapters are we talking about?
Amelia: All the ones marked "SVG 1.1 only" in the updated changes appendix.
Dirk: Okay, so should we try to add stub pages with the build?
Amelia: I will look into whether it is possible. Otherwise, will need to see if W3C admin can set up server redirects. And will also need to get a quick republication with those corrections.
RESOLUTION: If possible, add stub pages to spec for SVG 1.1 chapters that no longer exist, redirecting to correct specs for the content.
Dirk: To clarify, with the new edits, we want to add a class for both cr1 and cr2?
Amelia: Yes. Maybe not the best design. Was trying to minimize the changes. `changed-since-cr1` class adds styling. `cr2` class changes the date.
`class="changed-since-cr1 cr2"`
Dirk: One note, only normative changes really need an entry in the changes list. Editorial changes don't need an entry (although they could have them).
Tav: Might help not to add too many minor editorial notes.
Amelia: Agreed. Major editorial changes can be mentioned, but not typo fixes and so on.
Dirk: Thanks Amelia for clean-up PRs on changes and build. Still reviewing the build system changes.
Amelia: I'm also trying to review and merge outstanding PRs today.
Dirk: On PRs, to Tav: Does your PR cover most of the outstanding issues brought up in the internationalization review?
Tav: Some of them. A lot were just clarifying, but there are a few issues that I'm still working through to figure out what changes are needed.
Dirk: I will try to review the PR tomorrow.
Tav: Would be good to get feedback from the Internationalization reviewers.
Amelia: Can you ping the commenters on the PR itself, see if we can get confirmation that it address the issues.
Amelia: We have a charter extension til the end of November!
https://www.w3.org/2017/04/svg-2017.html
Amelia: Also, congrats to our new chair Dirk.
<ericwilligers> https://github.com/w3c/fxtf-drafts/issues/130
GitHub: https://github.com/w3c/fxtf-drafts/issues/130
Eric: I don't know much about it,
but it's been put on the CSS WG agenda, and is also marked as
needing SVG WG input.
... don't need to discuss now, but people should take a
look.
Dirk: Will need to review, but as I recall there were a few related issues.
Amelia: Based on the testing you reported in May, behavior was inconsistent between browsers. Which I think means we should spec a sensible behavior.
Dirk: It really depends on the specific cases, HTML elements having different behavior than SVG elements.
Amelia: Ah, so the inconsistencies are not between browsers, but between use cases. That is less useful.
Dirk: Yes, worried about breaking
content if we change things.
... If I look again, maybe we can discuss next week.
Eric: Sure.
GitHub: https://github.com/w3c/svgwg/pull/409
Amelia: I was tidying up the PR
for merging, but we did have comments concerned about the
breaking change.
... We had previously resolved on that change, wanted to
confirm before merging.
Dirk: Do we have usage statistics?
https://github.com/w3c/svgwg/issues/315#issuecomment-374485871
Yes, posted in the issue discussion ^^
Dirk: So usage is 0.002058%
<krit> V8SVGAElement_Target_AttributeGetter 0.002058%
Eric: That's tiny. We'd be happy to match other browsers. Also no desire to preserve the SMIL use case.
Amelia: We did discuss (in #312) also enhancing SVGAnimatedString with putForwards, so it can behave a little more like a DOMString, for cases like href where we can't change the actual IDL type.
Dirk: One issue is can we delay this change to 2.1?
Amelia: The longer its out there as SVGAnimatedString, the more potential for web compatibility issues.
Dirk: But there already is the compat risk. We have compatible implementations in all browsers.
<ericwilligers> My comment: https://github.com/w3c/svgwg/pull/409#discussion_r200943051
Amelia: The new attributes may also need to be removed if we don't get implementations. But that's less of an issue, if they're not breaking.
Dirk: I'm open to the change, I'm just worried we won't get implementations.
Amelia: Can we make the change, but mark it at-risk pending implementations? But I guess we still need to tell implementers what they should do.
Eric: What's the risk of no change?
Amelia: Risk is increased
incompatibility versus HTML.
... I'd recommend making the change, but we need to follow up
with browser bugs to make them update to match.
Eric: We really need some
commitments.
... We wouldn't make the change in Blink until there is
movement from other browsers.
Amelia: I can revert the changes
for `target` specifically in the PR, merge the other changes,
and then open up an issue specifically for `target`.
... We need commitments from multiple implementers to all make
the change at the same time if it is going to happen at
all.
github-bot, end topic
trackbot, end telcon
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/With/Dirk: With/ Default Present: AmeliaBR, Tavmjong, krit, ericwilligers Present: AmeliaBR Tavmjong krit ericwilligers No ScribeNick specified. Guessing ScribeNick: AmeliaBR Found Scribe: Amelia WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 13 Aug 2018 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]