- From: Piotrek Koszuliński <notifications@github.com>
- Date: Tue, 03 Jul 2018 10:12:35 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 July 2018 17:12:58 UTC
> So, creating DOM API might be more reasonable than space separated list attribute. While I agree that a DOM API may be more flexible (especially, if in the future, the configuration of enabled/disabled features would get more complex), I feel that any discussion about whether it needs to support `designMode` is missing the point. We have a coherent feedback from major rich-text editor authors. AFAIR none of us asked about doing anything with `designMode`. It's there, let it die. It shouldn't bother us. It shouldn't block anything. It's not something we need. We should be focused on designing a consistent and useful API for the future. Not on standardising the old mistakes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/176#issuecomment-402229483
Received on Tuesday, 3 July 2018 17:12:58 UTC