<scribe> scribenick: AmeliaBR
github: https://github.com/w3c/svgwg/issues/628
Dirk: Amelia, could you update?
Amelia: So, clearly an interop problem. I think its mostly browser bugs, but probably could use some spec clarifications.
Dirk: Are changes necessary for SVG 2.0
Tav: needs better tests
Amelia: Yes, either way tests are needed.
Tav: for Inkscape, it looks like we're ignoring text-anchor on tspan. which is our bug.
Dirk: Is there one rendering that is correct?
Amelia: Looks like librsvg. But there are differences about glyph selection as well as alignment, not sure which version is correct.
Dirk: Ok, so we need tests. Do we also need to change the spec.
Amelia: That might be easier to decide as we write the tests. Need to make sure that every test is clearly supported by spec text.
Dirk: Can we resolve then to revisit after testing?
Amelia: To confirm, that means we are sticking with the main idea of the spec, that text-anchor is only based on explicitly declared `direction`, not on directionality of text characters?
Tav: Yes, I don't think we want to change that now.
RESOLUTION: No major changes. Re-examine the spec text for clarifications after creating tests.
Chris: We have one week left
during charter review period.
... Response has been disappointing. I've sent out reminders,
but so far we don't have enough positive votes to keep the
group going.
... We have some comments in the Github Repo. Mostly concerns
about specific wording or references. I think we can sort most
of that.
... But the issue of incubation process is a bit of conflict.
But that's not an SVG-specific thing, it's common to many
groups.
... I've also submitted a new PR for our spec that will help us
keep track of testing status. It is based on CSS/Bikeshed tools
which grab tests and test results from WPT and injects little
info boxes into the spec itself.
Dirk: I think it's a great idea.
Amelia: The main issue is checking that it will work with all our spec build tools.
Chris: Yes, still need to test that. Other issue is whether the tests have the links to the spec they are testing. But we can add those if they are missing.
Amelia: That's the `<meta rel="help">` in the test files, right?
Chris: Yes, I think so.
github: https://github.com/w3c/svgwg/issues/618
<chris> https://github.com/w3c/svgwg/issues/629
Chris: I'd initially thought this was a CSS issue, but fantasai threw it back to us, because this really comes down to x and y and text-anchor.
Amelia: So the question is, if you have writing mode tb and direction rtl is start "top" or "bottom"?
Chris: Yes, and as fantasai suggested there may be complications with issue 629
Amelia: I'm not sure they are
really dependent on each other. It's about alignment in the
orthogonal direction.
... much of these may both be caused by SVG 1.1 spec text that
needs to change to match changed property definitions in
`writing-mode` and `dominant-baseline`.
... probably again, we need to take a test-first approach and
see if the spec actually defines behavior.
Dirk: But do we have agreement on what should happen?
Amelia: Maybe come back with tests for all the combinations, but no references & then we can go through and discuss what should happen.
github: https://github.com/w3c/svgwg/issues/617
Tav: This is a rather confusing algorithm, but I think I've figured out where the issue is. According to the prose, if a given character has both `x` and `dx` values, they get combined (set `x`, and then add `dx`), but according to the algorithm `dx` gets dropped in that case. And that's not what Inkscape or browsers do.
Chris: Are implementations consistent? Can we just adjust the algorithm to match?
Tav: I think everyone's consistent.
Chris: Have you figured out the suggested changes, in your last comment Tav?
Tav: I think so. Needs a review.
Dirk: Can you make it a proper PR?
Tav: Sure.
<chris> https://bfo.com/
Chris: And tag the original poster for review, who seems to be working on an implementation.
RESOLUTION: Fix algorithm to be consistent with SVG 1 and implementations (dx/dy add to x/y on same character).
Amelia: We have a few PRs on the spec and on WPT that are stuck at "Changes requested". If people can follow up on their PRs, or if you won't have time to follow-up, then ask someone else to take over.
trackbot, end telcon
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/content/conflict/ Default Present: stakagi, krit, Tav, AmeliaBR, ericwilligers, chris Present: stakagi krit Tav AmeliaBR ericwilligers chris Found ScribeNick: AmeliaBR Inferring Scribes: AmeliaBR WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 21 Jan 2019 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]