On 5/2/24 16:43, Mason Freed wrote:
On Wed, May 1, 2024 at 10:04 AM fantasai <[email protected]> wrote:

     1. The *revised design* should get feedback *from authors*. For example by:
         1. Shipping your revised implementation in test builds so devs can
            try them out/and/
         2. Posting about the new model in your DevRel channels so they know
            about it and know to give feedback!
         3. Presenting at e.g. CSS Day, and ideally inviting feedback on an
            implementation the audience can test out and is excited about
            using soon, /but is still possible to change in response to their
            feedback./
         4. Posting to the CSSWG blog about the revised spec and inviting
            feedback from authors (which wasn't done when the spec was
            republished in March).
         5. and any other channels that make sense.

I (still) agree with this point. I believe we’ve done most all of these things over the last two years as we’ve been developing this feature.

1. Not done.
2. Completed 2 days ago.
3. Not done.
4. Not done.
5. Unclear.

"most of these things" is not true.

     1. The feature should get *horizontal review at W3C* and especially
        *address accessibility*. This should include:
         1. Sending request to TAG, i18n, a11y, etc. in the appropriate
            channels
            
<https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review>.
         2. Documenting any accessibility concerns, intentions, and best
            practices in the spec, and addressing issues that come up.
         3. Preparing to teach and promote accessible use of this feature
            together with appropriate markup.

I agree. We’ve done some of that, but we’d be happy to have input on venues that we should additionally contact.

You still haven't done #1, even though I gave you the how-to link.

     1. The edited spec should get a *last call review in the CSSWG*.
         1. By sending a review request to the CSSWG/www-style noting the
            revisions that /have landed/ and are ready to review, and,
            ideally, noting that Chrome intends to ship soon so that reviewers
            can prioritize accordingly.

Ok, we will get this process started.

What do you think is the "process" for this and why would you wait to start it until after you've already shipped?

If we need to make such dramatic changes after shipping, then we’ll make them!

Great! I just spent my weekend reviewing the spec for you. Let's see how genuine your offer is.

I think it’s a bit unfair to call this “shipping the first draft”.

I didn't call it one.

Your responses in this thread are often not to what I've actually been writing. Please be less sloppy in your reading, it's kindof obnoxious.

~fantasai

--
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5a762523-a2a7-40c6-b294-9b6a0c309e0d%40inkedblade.net.

Reply via email to