Re: [w3c/editing] When an 'insertHTML' command should be applied as sibling or child of a <font> element ? (#191) from Johannes Wilm on 2019-04-08 (public-webapps-github@w3.org from April 2019)

From: Johannes Wilm <notifications@github.com>
Date: Mon, 08 Apr 2019 14:42:49 -0700
To: w3c/editing <editing@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/editing/issues/191/481019406@github.com>

I think the sudden appearance of the obsolete `<font>` element [1] is likely one of the first signs to JS devs that contenteditable is unmaintained. I remember running into that around 2012. I don't think any solution that involves HTML 3 elements that have been deprecated since should be encouraged in 2019. Even if that means breaking with the current behavior of all browsers.

[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font

-- 
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/191#issuecomment-481019406

Received on Monday, 8 April 2019 21:43:13 UTC