W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

[Bug 11797] Declarative way to get formatting UI for contenteditable="" (as in <video controls=""> but for text editing)

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Mar 2013 00:19:08 +0000
To: public-webapps@w3.org
Message-ID: <bug-11797-2927-Sp0nxrmoL2@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11797

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEW
                 CC|                            |public-webapps@w3.org
          Component|HTML                        |HTML Editing APIs
           Assignee|ian@hixie.ch                |ayg@aryeh.name
            Product|WHATWG                      |WebAppsWG
         QA Contact|public-html-bugzilla@w3.org |sideshowbarker+html-editing
                   |                            |-api@gmail.com
            Summary|<richtext> </richtext> This |Declarative way to get
                   |will provide a default rich |formatting UI for
                   |text widget which is        |contenteditable="" (as in
                   |scriptable and should also  |<video controls=""> but for
                   |support the Rich Text       |text editing)
                   |Format (RTF) Default widget |
                   |implementation should be a  |
                   |text area with richtext     |
                   |controls above it. This     |
                   |will enable browsers to     |
            Summary|pr                          |
   Target Milestone|Unsorted                    |---
           Severity|normal                      |enhancement

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Moving this to the HTML Editing APIs spec for now. If this is something that
makes sense to add, then I'll be happy to coordinate and provide the markup
side of this, but really I think the HTML Editing APIs spec needs to be the
place where we define what it does.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 19 March 2013 00:19:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT