– DRAFT –
(MEETING TITLE)

Support pathLength via CSS

w3c/svgwg#773

viralipurbey: This is a follow up: Should we extend the property unit from number to length.

viralipurbey: For now we just extend the existing attribute to presentation attribute.

viralipurbey: While implementing, we signaled the implementation to Firefox

viralipurbey: It has a lot of complexity to support length.

viralipurbey: We should take it as a different issue and land the presentation attribute change in the spec.

nzimmermann: Don't mind to take it into 2 steps.

krit: Might there be a complication if we change unit from number to length?

viralipurbey: we can talk about it later?

viralipurbey: It is already a number unit. So don't see an issue

krit: No objection from my side.

RESOLUTION: pathLength attribute will get a presentation attribute with the CSS property being path-length taking a number unit only for now

ACTION: viralipurbey to prepare spec edits. dmangal and nzimmermann to review the PR

Multi-Page support

w3c/svgwg#157

krit: This is a request to support multi pages support from the SVG draft 1.2 in SVG 2.

nzimmermann: I support to reject the request. CSS Paged Media is better suited for this task

nzimmermann: it is hard to implement too

krit: Out of charter scope anyway

caribou: correct

RESOLUTION: Multi pages will not get adapted in SVG2

Publish current status of SVG

w3c/svgwg#938

caribou: Karl was working on supporting bikeshed for the spec

caribou: We are making progress on the editors draft but should also focus on an actual publication

krit: would you prefer using the old system or can we wait for bikeshed migration?

caribou: Maybe it is ok to wait for the bikeshed migration

krit: Lets wait for Karl to provide feedback on the current status before we make the decision.

SVGPathSegment should be a dictionary, not a [NoInterfaceObject] interface

w3c/svgwg#1082

Vinay: this is about the new data API

Vinay: Previous old API using DOM was deprecated 15 years back. Chromium has deprecated.

viralipurbey: Edge cases were not defined properly in the old API and remove

viralipurbey: the new API was added. Last year Firefox implemented it.

viralipurbey: Chromium also plans to implement.

viralipurbey: We should use a dictionary rather than NoInterface for SVGPathSegment

viralipurbey: Even Firefox ran into issues when adapting the new API and uses dictionary

krit: dictionary is more flexible anyway. Any downside for it?

viralipurbey: we don't see any. Even our polyfill is working fine with that.

viralipurbey: sugesting to got from

viralipurbey: going from float to unrestricted float to support 0 and NaN types.

viralipurbey: earlier it gave type error

viralipurbey: Firefox also did the suggested change

RESOLUTION: SVGPathSegment defined as dictionary instead of NoInterfaceObject and make value unrestricted float from float

New Interface SVGPathSegment: segments should be more editable

w3c/svgwg#974

viralipurbey: Same thing: Previously there was a CTOR for SVGPathElement. With dictionary, this is not valid.

viralipurbey: All new code doesn't use the CTOR.

viralipurbey: no backwards compatibiliy since it hasn't been implemented anywhere

nzimmermann: My concern is the SVG Path spec which is WD since 2015 last updated

nzimmermann: it is not in SVG2 but SVG Path

nzimmermann: SVG Path also has new features that haven't been implemented and have many open issues

nzimmermann: So where should we put all this?

krit: It is still part of SVG2 but the interfaces are missing and in SVG Path spec.

<karlcow> Close in webkit bugs https://bugs.webkit.org/show_bug.cgi?id=168519

nzimmermann: Question is where we normatively define SVGPathSegment? Is it still in SVG 2 or SVG Path spec (which never reached CR)

<caribou> https://www.w3.org/TR/SVG2/paths.html

<karlcow> https://www.w3.org/2011/10/27-svg-irc#T18-23-23

krit: the entire interface section has been removed from SVG 2

<caribou> https://www.w3.org/TR/SVG2/paths.html#InterfaceSVGPathElement leads to nothing

<karlcow> https://w3c.github.io/svgwg/specs/paths/

<karlcow> https://w3c.github.io/svgwg/specs/paths/#InterfaceSVGPathSegment

krit: Path Spec is out of scope from charter. I suggest to create a proposal to re-add the interfaces. And all members agree on get re-added to SVG 2.

nzimmermann: agree

ACTION: viralipurbey to create a PR to re-introduce SVG Path interfaces from SVG Path spec into SVG 2 for approval of the WG

dmangal: Does introducing dictionaries make path data editable?

dmangal: we need to be sure it does

viralipurbey: I don't see an issue. The Polyfill does use the dictionary approach and has no issue with edtiablity

RESOLUTION: Drop SVGPathElement constructor in favor for dictionary model

RRSAgent: make minutes