- From: Paul LeBeau <paul.lebeau@gmail.com>
- Date: Sat, 21 Mar 2015 18:01:37 +1300
- To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Cc: www-svg <www-svg@w3.org>
- Message-ID: <CACfsppA9-jVhZuM0n7pNeo3+WU8JLiadoE45vKgKv9jiUERWKQ@mail.gmail.com>
Thanks Amelia. On 21 March 2015 at 08:53, Amelia Bellamy-Royds < amelia.bellamy.royds@gmail.com> wrote: > Paul: > > Cameron should be following up [1], but the main gist was that `fill` and > `stroke` should become shorthand properties, and each one should have a > sub-property in which you were able to specify the reference bounding box > to use for each fill/stroke paint server. > > Key points of the debate: > > - Everyone liked the idea of having control over which bounding box to use > for paint servers. > > - However, that control would have to be linked to specific uses of that > paint server (e.g., as stroke paint vs as fill paint), so a single > over-riding property doesn't seem appropriate. > > - Everyone agreed that we should try to maintain a consistent syntax with > other properties that relate to object bounding boxes. > > - Currently, the masking spec [2] uses a separate property (mask-origin) > to declare the reference box (with the option of declaring it in the mask > shorthand property) while clipping paths only have a single, multi-part > property. So the "consistency" goal doesn't really lean one way or another. > > - Although no one brought it up on the call, the current SVG 2 syntax for > stroke and fill [3] also allows you to specify a size for each paint > server, but it is not currently described in terms of reference boxes. > > - Because SVG2 fill and stroke can both be a list of paint servers, > authors should have the choice of specifying a single reference box for all > of them or separate reference boxes for each. The general CSS rules for > "list" values and shorthand properties support this if there is a separate > property. > > If you're interested in coming up with more use cases, suggestions and/or > a full proposal, please do so. > > AmeliaBR > > [1]: ACTION-3772 http://www.w3.org/Graphics/SVG/WG/track/actions/3772 > [2]: http://dev.w3.org/fxtf/css-masking-1/ > [3]: https://svgwg.org/svg2-draft/painting.html#SpecifyingPaint > > > > On 20 March 2015 at 11:36, Paul LeBeau <paul.lebeau@gmail.com> wrote: > >> In the 11/12 March telecon there was an ACTION item to follow up on this >> suggestion. I haven't seen anything, so thought I'd do a reminder bump. :) >> >> I'm not sure I completely followed the gist of where the telecon >> discussion was leading. Can someone explain please? >> >> Paul >> >> >> On 8 March 2015 at 20:41, Paul LeBeau <paul.lebeau@gmail.com> wrote: >> >>> The gettBBox() function now allows you to control which parts of the >>> shape are included in the bounding box. So I suggest that we expose that >>> functionality as a property. >>> >>> bbox-rendering = "[fill] [stroke] [markers]" >>> >>> The purpose being is that it would affect the bbox used for >>> "objectBoundingBox" units. The name is a placeholder in lieu of something >>> better. >>> >>> There was a discussion related to this concept in Feb 2014 wrt HTML >>> clipping and masking, but AFAIK this hasn't been suggested in the SVG >>> context. (maybe I am wrong?) >>> >>> >>> So I submit the following for consideration: >>> >>> http://www.paullebeau.com/svg2/bbox-rendering/bbox-rendering.html >>> >>> >>> Paul >>> >>> >> >
Received on Saturday, 21 March 2015 05:02:25 UTC