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 22:36:47 +0000 (UTC)
To: w3c/editing <editing@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/editing/issues/191/481033446@github.com>

The place where I encountered the font-element, if I recall correctly, was when hitting enter in the middle of an inline element that was styled in a certain way. This happened on Chrome.
Would it not be possible to make a general rule that the browser should never create pre-HTML5 elements as part of contenteditable and then grep for all instances of font-elements in the source code and replace them with spans? Possibly with inline styles.

-- 
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-481033446

Received on Monday, 8 April 2019 22:37:12 UTC