[Bug 19058] New: <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19058

           Summary: <richtext> </richtext> This will provide a default
                    rich text widget which is scriptable and should also
                    support the Rich Text Format (RTF) Default widget
                    implementation should be a text area with richtext
                    controls above it. This will enable browsers to pr
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, mail@tobyinkster.co.uk,
                    ayg@aryeh.name, mounir.lamouri@gmail.com


This was was cloned from bug 11797 as part of operation LATER convergence.
Originally filed: 2011-01-19 00:42:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2011-01-19 00:42:49 +0000 
--------------------------------------------------------------------------------
Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
<richtext> </richtext>
This will provide a default rich text widget which is scriptable and should
also support the Rich Text Format (RTF)
Default widget implementation should be a text area with richtext controls
above it. This will enable browsers to provide native support for rich /
advanced text entry and editing.

Posted from: 41.220.69.7
================================================================================
 #1   Aryeh Gregor                                    2011-01-19 09:27:48 +0000 
--------------------------------------------------------------------------------
This is kind of an interesting suggestion, actually.  Maybe this could be done
by having some kind of "controls" attribute for contenteditable, à la video.
================================================================================
 #2   Toby Inkster                                    2011-01-20 14:37:39 +0000 
--------------------------------------------------------------------------------
contenteditable is such a poorly designed feature. It's essentially useless
without Javascript. Its design is inherited from original proprietary
implementations, and I'd like to think that if it had originated in the HTML WG
instead, we'd have something much better.

Something like:

<textarea type="text/html">...</textarea>

would be far preferable.
================================================================================
 #3   Ian 'Hixie' Hickson                             2011-02-16 08:18:48 +0000 
--------------------------------------------------------------------------------
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: https://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 Tuesday, 25 September 2012 22:01:58 UTC