Re: [w3c/editing] [charter] execCommand spec should be in scope (Issue #432)

I didn't attend Editing TF meetings back in the day.

I generally have little confidence in the timelines in W3C WG charters when specs are supposed to be done. As long as this spec is on the Rec track I would be satisfied.

> Unless the plan is to write the spec in a merely descriptive manner ("Safari does A, Chrome does B, Firefox does C"), there will be some challenges to make browsers behave the same (and thereby follow a specific spec).

I envision a rough process like this:

1. Write the spec for any common ground where we already have interop, and verify with tests. Leave other parts as UA-defined, with tentative tests that demonstrate lack of interop.
2. Discuss if we can align on the UA-defined bits. If so, specify the behavior we want and fix browsers accordingly.
3. Repeat step 2 until either no UA-defined bits are left or we've reached diminishing returns.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/432#issuecomment-1593214918
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/432/1593214918@github.com>