- From: Johannes Wilm <notifications@github.com>
- Date: Thu, 21 Sep 2023 05:57:43 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 21 September 2023 12:57:49 UTC
Hey, yes so to be clear: Simon will investigate some.And then that might end up in sone spec text and a bug report for various browsers. But then there is no guarantee that the bug report will be acted upon. Contenteditable bug reports can at times sit around for 15+ years without anything happening as it's mostly a legacy feature. On Thu, Sep 21, 2023, 14:40 joanmarie ***@***.***> wrote: > Hey, could you make separate issues for each of those points? > > Done. I was erring on the side of caution (Does this working group really > want a bunch of issues all for a feature that authors seem to be > discouraged from using?). But now that I know this is your preference, I > will do so going forward. I'll try not to file too many more. 😉 > > — > Reply to this email directly, view it on GitHub > <https://github.com/w3c/editing/issues/437#issuecomment-1729488349>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAERMOC6FLRN2LS4XSYX53LX3QYVJANCNFSM6AAAAAA4HOREMU> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/437#issuecomment-1729514127 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/437/1729514127@github.com>
Received on Thursday, 21 September 2023 12:57:49 UTC