W3C home > Mailing lists > Public > public-webplatform@w3.org > August 2014

Re: Compatibility tables are now live!

From: Eliezer Bernart <eliezer.bernart@gmail.com>
Date: Sun, 3 Aug 2014 16:24:33 -0300
Message-ID: <CAAECTTQQpBJmksxx-GvPYCDjEU6m=HsmbRb3DsXUJ+-Q6vYJ4A@mail.gmail.com>
To: Renoir Boulanger <renoir@w3.org>
Cc: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>, List WebPlatform public <public-webplatform@w3.org>
Hello Amelia, Renoir and all,

* We should still have a top-level check box to suppress printing the
> compatibility section altogether.
>

I just created a new property to store this information, if this option is
checked then the fields in the form will be displayed, otherwise, no
Compatibility Section will be displayed in the page.

http://docs.webplatform.org/test/Property:Has_compatibility_table

* The default value for format should be assigned in the
> Compatibility_Section template using the {{{format|table}}} structure.  The
> default you specify in the form only applies to new pages, not existing
> pages, so existing pages have an error message instead of a table, see
> http://docs.webplatform.org/test/dom/apis/document/getElementById
>

Just got that issue. I assigned alternative values if a page has some blank
values, if they are filled the actual value will be used:

{{#tag:compatibility || feature={{{Compatibility feature |
{{#titleparts:{{PAGENAME}} || -1}} }}} | topic={{{Compatibility topic |
{{#titleparts:{{PAGENAME}} | 1}} }}} | format={{{Compatibility format |
table }}} }}

But I was not able to get ride of the "None" option in the form when the
"Compatibility format" property still is empty.

* The auto-complete doesn't seem to be working for feature, so it's not
> really clear what value to put here.
>

Renoir will implement this function soon.

* The labels should clearly indicate that the topic and feature fields are
> only required if the WPD names don't match the MDN names.  (And then have
> some information on how people could figure out what the MDN name would be!)
>

I'm not so good writing clearly labels, can someone give me some help?

If someone catch other issues, or think that something needs to be
improved, just let me know.

Amelia, are the problems solved now, or do you think we should improve
something else? Thanks for pointing out!
Renoir, thanks for the help!

Following the links of pages and templates:

*Properties*:
Compatibility_format ->
http://docs.webplatform.org/test/Property:Compatibility_format
Compatibility_topic ->
http://docs.webplatform.org/test/Property:Compatibility_topic
Compatibility_feature ->
http://docs.webplatform.org/test/Property:Compatibility_feature
Has compatibility table ->
http://docs.webplatform.org/test/Property:Has_compatibility_table

*Templates:*
http://docs.webplatform.org/test/Template:Compatibility_Form_Section
http://docs.webplatform.org/test/Template:Compatibility_Section

*Test pages*:
http://docs.webplatform.org/test/css/properties/border
http://docs.webplatform.org/test/css/properties/text-shadow
http://docs.webplatform.org/test/css/properties/text-align




Eliezer

www.eliezerb.com.br
@eliezerbernart <https://twitter.com/eliezerbernart>
eliezerb


On Sun, Aug 3, 2014 at 1:33 PM, Renoir Boulanger <renoir@w3.org> wrote:

> Hi all, see comments inline
> --
>
> On August 1, 2014 4:32:45 PM EDT, Amelia Bellamy-Royds <
> amelia.bellamy.royds@gmail.com> wrote:
> >Hi Eliezer,
> >
> >Great work.  A couple notes:
> >
> >* We should still have a top-level check box to suppress printing the
> >compatibility section altogether.
>
> I agree.
>
> >* The default value for format should be assigned in the
> >Compatibility_Section template using the {{{format|table}}} structure.
> >The
> >default you specify in the form only applies to new pages, not existing
> >pages, so existing pages have an error message instead of a table, see
> >http://docs.webplatform.org/test/dom/apis/document/getElementById
>
> I didn't  know it was impossible to force a default value on existing
> pages that we can change.
>
>
> >* The auto-complete doesn't seem
> >to be working for feature, so it's not
> >really clear what value to put here.
>
> This isn't done yet. Ill have to make it.
>
> In the meantime a notice that links to the human readable json file[0][1]
> and the github repo[2] might be useful.
>
>   [0]: http://docs.webplatform.org/compat/data-human.json
>   [1]: http://docs.webplatform.org/compat/data.json
>   [2]: https://github.com/webplatform/compatibility-data
>
> >* The labels should clearly indicate
> >that the topic and feature fields are
> >only required if the WPD names
> > don't match the MDN names.  (And then
> >have some information on how
> >people could figure out what the
> >MDN name would be!)
>
> Fair point, but will not be the case advitam æternam.
>
> That's where default value based on URL was expected to be useful.
>
> >Following up on Renoir's suggestion,
> >one option would be to have a
> >checkbox
> >that says "Use default values", and
> >only show/enable the other fields if
> >that check box is turned off.  If possible, there could be some sort of
> >error message that displays on the
> >form itself if the default values
> >won't return any data.
>
> I can change the output to return no error instead. Logic in mediawiki
> markup is sketchy.
>
> HTH
>
> Renoir
> ~
>
Received on Sunday, 3 August 2014 19:25:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:03 UTC