- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2018 19:57:10 +0000
- To: public-svg-issues@w3.org
Does anyone have any outstanding issues on this, or can this be closed? Teleconference minutes (reposting what Github-bot posted in the wrong issue): The Working Group just discussed `Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript`. <details><summary>The full IRC log of that discussion</summary> <Chris__> topic: Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript<br> <Chris__> github: https://github.com/w3c/svgwg/issues/291<br> <krit> AmeliaBR: we have interfaces that are defined as NoInterfaceObject but other object types which implement these infterfaces which have those properties on them<br> <krit> AmeliaBR: so you could access those constants but not as a static item<br> <krit> AmeliaBR: usually constants are property of a class<br> <krit> AmeliaBR: need to recall. it is from 2016<br> <krit> krit: those are mixing and get implemented by those classes. So they actually are part of those classes implementing them.<br> <krit> krit: not sure where the issue is?<br> <krit> AmeliaBR: those are legacy features and not used on the web. Keep them close to SVG 1.1<br> <krit> AmeliaBR: not sure what is required.<br> <krit> krit: are those interfaces implemented already?<br> <krit> krit: we were asked to re-add interfaces not because they are used but because they are implemented widely<br> <AmeliaBR> Here's the last update on implementation https://github.com/w3c/svgwg/issues/291#issuecomment-254204205<br> <krit> Chris__: so we have interfaces that are not used but implemented.<br> <krit> Chris__: seems like some ppl argue it shouldn't be exposed.<br> <AmeliaBR> SVGUnitTypes was implemented, and was re-introduced to the spec. SVGZoomAndPan wasn't well implemented cross-browser, and that's whay it wasn't changed at the time.<br> <krit> Chris__: Firefox seems to expose and implement it directly and does seem to have tests<br> <krit> AmeliaBR: there are 2 different causes.<br> <krit> AmeliaBR: no decision has been made and issue was reopened. Not implemented browsers anyways.<br> <krit> krit: they are not implemented? because I think they are.<br> <AmeliaBR> s/no decision/for SVGZoomAndPan/<br> <Chris__> https://bugzilla.mozilla.org/show_bug.cgi?id=1241898<br> <krit> Chris__: original comment was about aligning implementations so we have 2 implementations, Blink and Firefox<br> <AmeliaBR> s/for SVGZoomAndPan/for SVGZoomAndPan, no decision/<br> <krit> ericwilligers: we could still remove those interfaces if they are not sued<br> <krit> s/sued/used/<br> <krit> Chris__: yes we could<br> <krit> Chris__: not sure what is proposed is better<br> <krit> AmeliaBR: I don't think we are getting anywhere on this on the call. We should ping ppl if this is still an issue or if they are happy with changes that were made.<br> <krit> Chris__: agree. Will post on the issue and ask for comments.<br> <Chris__> github: https://github.com/w3c/svgwg/issues/269<br> </details> -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/291#issuecomment-361366921 using your GitHub account
Received on Monday, 29 January 2018 19:58:15 UTC