- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Feb 2011 08:18:48 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11797
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |LATER
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-16 08:18:48 UTC ---
IE5 had <richedit>, IIRC. Microsoft dropped it. Do we know why? It would be
useful to find out what their reasoning was, to make sure we didn't make the
same mistake.
In the meantime, I'm going to mark this LATER since it's a _major_ new feature
and now isn't a particularly convenient time to be adding new features.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Partially Accepted
Change Description: none yet
Rationale: We should wait for implementations to catch up before adding new
features, especially in the space of rich text editing where there's a lot of
work to be done just in getting the existing features interoperably
implemented.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 16 February 2011 08:18:51 UTC