00:00:00 00:20:02 AmeliaBR: ping we're back 00:21:31 ScribeNick: heycam 00:22:10 Topic: SVG Integration spec 00:22:18 nikos: Bogdan will be an editor of this spec 00:22:31 BogdanBrinza: there are a few issues that might be worth discussing and knocking out 00:22:39 ... might be more of an FYI 00:23:01 https://svgwg.org/specs/integration/ 00:23:22 https://svgwg.org/specs/integration/#issue1 00:23:37 ... first issue is all the different scenarios of SVG integration 00:23:41 ... foreignObject, CSS context 00:24:15 ... the thing that is mostly concerned for CSS/SVG implementaors is sizing SVG documents in CSS, sizing HTML content in foreignObject 00:24:24 ... can you give me a sense of the relative priority of other things? 00:24:39 ... metadata? 00:24:43 heycam: not important, focus on the sizing 00:24:54 BogdanBrinza: so with initial containing block with foreignObject viewport, I don't think this is an issue 00:25:03 ... for CSS sizing I have half of the change in progress, still working on that 00:25:10 ... don't think anything else in issue 1 needs talking now 00:25:15 https://svgwg.org/specs/integration/#issue2 00:25:36 ... issue 2, this talks about referencing the Fetch algorithm 00:26:18 heycam: this is about CORS etc. 00:26:29 BogdanBrinza: not sure how this applies to referencing modes though 00:27:23 heycam: sounds like it might be better to reference the Fetch spec from different places in the SVG spec then, e.g. in the definition etc. 00:27:31 ed: agreed 00:27:43 AmeliaBR: maybe we'd want to use Anonymous mode for resource documents for example 00:27:56 BogdanBrinza: sounds likes an extension of the referencing mode rather than something about the Fetch algorithm 00:28:16 AmeliaBR: I don't think we have any referencing modes where Anonymous mode is explicitly mentioned 00:29:37 https://svgwg.org/specs/integration/#issue3 00:29:40 BogdanBrinza: issue #3 now 00:29:47 AmeliaBR: animations in resource documents 00:30:22 BogdanBrinza: just looking at the issue and the context around the issue, I don't think anything int he current wording suggests they shouldn't run 00:30:41 AmeliaBR: an example is using content from another file, and that file has declarative animations, then should your reused copy of that reflect those animations 00:30:51 BogdanBrinza: why not? 00:30:57 AmeliaBR: I don't see an issue 00:31:05 BogdanBrinza: so you define the resource, as part of the definition there are some animations 00:31:14 ... saying there shouldn't be any animations running doesn't make sense to me 00:32:00 AmeliaBR: one issue that has come up before which we have waffle language in SVG 2 about is that resource documents don't have a medium, so has problems with media queries, resolving percentages 00:32:44 Rossen: 300x150! 00:32:48 heycam: yes, why not 00:33:26 BogdanBrinza: so if the resource references percentages how do they get resolved 00:33:27 ed: right 00:33:53 BogdanBrinza: similar to background-image? 00:33:56 AmeliaBR: this is SVG resources 00:34:17 ed: say you referenced an external gradient file 00:34:25 ... fill: url(externalfile.svg#gradient) 00:34:46 Rossen: how is this different frmo use? 00:34:51 ed: it's not, but it's not defined well there 00:35:15 AmeliaBR: percentages come up in use elements. in same document use elements, percentages are resolved on the original document not the referncing element 00:35:17 Rossen: not for us 00:36:24 AmeliaBR: right now if you have an SVG file with nested viewBoxes, and you want to reuse content into the local viewBox, it doesn't adjust to the local definition of what 100% is 00:36:30 Rossen: is this based on implemnetations or spec? 00:36:39 AmeliaBR: I'm pretty sure it's in the spec, not necessarily intentionally 00:36:45 ... but it is consistent everywhere we tested it 00:37:14 ... the other thing is that most implementations don't run CSS in resource documents, so if you have a