GroupData and CSS

[Eric Shepherd]

I don't see a way to add CSS properties to the GroupData template for a
given specification. This comes up sometimes; for example, the Pointer
Events spec includes the touch-action CSS property, which lets you
control the manner in which the user can interact with the element by touch.

Do we want to consider adding support for that to GroupData and the
APIRef macro? There must be other cases where this comes up.

--

Eric Shepherd
Senior Technical Writer
Mozilla Developer Network <https://developer.mozilla.org/>
Blog: https://www.bitstampede.com/
Twitter: http://twitter.com/sheppy
Doodle: http://doodle.com/the.sheppy

[Sebastian Zartner]

I agree that it would be nice to have that kind of linking between
sections. Similar connections exist e.g. HTML and APIs or SVG and CSS,
which could also profit from a better a better sidebar reference.

Note that the group info for CSS properties, @-rules and so on is
currently stored within CSSData.
So, to avoid redundancy, I see two options:

1. Add the CSS related items to GroupData, change APIRef to also read
the group info for CSS related data and CSSRef (and maybe other
macros) to use the group info from GroupData - or alternatively create
a new macro that combines the logic of APIRef and CSSRef - and remove
the "group" attributes from CSSData.
2. Change APIRef to read the group info for CSS related items from
CSSData and change CSSRef to read the group info of API related items
from GroupData.

I lean towards option 1, as it summarizes the group information at a
single place and allows to incorporate more related info, but it also
requires more work.

Sebastian

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
> MDN contributor guide: http://bit.ly/ContributorGuide

[Eric Shepherd]

I agree; I think that's the way to go. We need to stop taking shortcuts
when building things like this and do it the right way, even if it takes
longer. It's helpful that we have so many more contributors that are
getting really great at building macros these days, because we can get
more and better ones made.


------------------------------------------------------------------------
*From:* Sebastian Zartner
*Sent:* Tuesday, Sep 13, 2016 9:25:01 AM EDT
*To:* Eric Shepherd
*Cc:* MDC Mailinglist
*Subject:* [dev-mdc] GroupData and CSS

> 1. Add the CSS related items to GroupData, change APIRef to also read
> the group info for CSS related data and CSSRef (and maybe other
> macros) to use the group info from GroupData - or alternatively create
> a new macro that combines the logic of APIRef and CSSRef - and remove
> the "group" attributes from CSSData.
> 2. Change APIRef to read the group info for CSS related items from
> CSSData and change CSSRef to read the group info of API related items
> from GroupData.
>
> I lean towards option 1, as it summarizes the group information at a
> single place and allows to incorporate more related info, but it also
> requires more work.

[Sebastian Zartner]

I suggest to wait for some more feedback and then file a bug for it
once we agreed on it.

Sebastian

On 13 September 2016 at 17:48, Eric Shepherd <eshe...@mozilla.com> wrote:
> I agree; I think that's the way to go. We need to stop taking shortcuts when
> building things like this and do it the right way, even if it takes longer.
> It's helpful that we have so many more contributors that are getting really
> great at building macros these days, because we can get more and better ones
> made.
>
>

> ________________________________
> From: Sebastian Zartner
> Sent: Tuesday, Sep 13, 2016 9:25:01 AM EDT
> To: Eric Shepherd
> Cc: MDC Mailinglist
> Subject: [dev-mdc] GroupData and CSS

>
> 1. Add the CSS related items to GroupData, change APIRef to also read
> the group info for CSS related data and CSSRef (and maybe other
> macros) to use the group info from GroupData - or alternatively create
> a new macro that combines the logic of APIRef and CSSRef - and remove
> the "group" attributes from CSSData.
> 2. Change APIRef to read the group info for CSS related items from
> CSSData and change CSSRef to read the group info of API related items
> from GroupData.
>
> I lean towards option 1, as it summarizes the group information at a
> single place and allows to incorporate more related info, but it also
> requires more work.
>
>
> --
>
> Eric Shepherd
> Senior Technical Writer
> Mozilla Developer Network

[Jean-Yves Perrier]

Yes please, Sheppy file a bug, so we can discuss the feature and plan to
add it in a future sprint, after review.

As decided in the London All Hands, Florian is the one reviewing changes
to any macro.

--
Jean-Yves

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
> MDN contributor guide: http://bit.ly/ContributorGuide
>

--
Jean-Yves Perrier
Senior St. Project Manager, Developer Documentation / MDN