W3C home > Mailing lists > Public > www-svg@w3.org > December 2016

[css-transforms-1] Open Issues

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sat, 31 Dec 2016 16:24:53 +0330
To: "www-style@w3.org" <www-style@w3.org>, "public-fx@w3.org" <public-fx@w3.org>, www-svg <www-svg@w3.org>
Message-ID: <e44080ca-bf32-d058-362c-c30b3e79d0a2@inkedblade.net>
Hey everyone,
Since we *ostensibly* have a goal of getting CSS Transforms to CR,
I have compiled a list of all issues that require further discussion
and put them on the agenda for Seattle for you to discuss. Per WG
resolution to re-split the module, this list only includes the issues
relevant to 2D transforms.

You can find this list here:
It covers May 2012 through today, including discussions in Bugzilla,
www-style, public-fx, and GitHub. You're welcome. Please humor me
by being prepared to discuss the issues.

Fwiw, none of them seem particularly intractable, merely thus far not
entirely tracked. Issues that appear to need WG discussion (or at least,
the half of the WG that understands the issue) are marked as =WG=.
Issues that merely need the editors to do something are marked =ED=.
I will note that Transforms is not a spec that I follow, so this is
all approximate to the best of my limited ability.

The issues list is compiled by hand using a text format derived from
the lists that Hixie used to maintain of CSS2.1 issues reported to
www-style. It is formatted with a script which you can find here:
The script also includes documentation on the format.

For an editor to declare an issue as closed, the procedure is as follows:

1. Post a message saying whether or not changes where made and why,
    and if changes were made, describe them or link to them as
    appropriate. If a WG resolution was made, link to the minutes.

    Here is an example of such a message:

    (As I could not find such a message in most of the Transforms
    threads, I assumed no conclusion was reached for most of the

2. If the discussion is being tracked somewhere (like, we're in a
    bug database, or you're maintaining an out-of-band issues list
    like the DoC above), change the associated status to Closed.

    To do this in the issues-list format
      a. Add a link to the concluding message as a Response: line
         so that the conclusion is tracked.
      b. Change the status from Open to Closed: [appropriate keyword]
      c. Optionally, add lines for Changes: or Resolved: or Verified:
         (See documentation.)
    Regenerating the HTML will color the issue appropriately.

Follow-ups to public-fx, please.

Received on Saturday, 31 December 2016 12:55:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:07 UTC