[Bug 14455] New: When tapping within a contenteditable, mobile browsers display a VKB that hogs the screen. But what if users don't want to enter any new text? They might instead make a selection, copy it, drag to move it, format it, or paste in something else. Ideally

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14455

           Summary: When tapping within a contenteditable, mobile browsers
                    display a VKB that hogs the screen. But what if users
                    don't want to enter any new text?  They might instead
                    make a selection, copy it, drag to move it, format it,
                    or paste in something else.  Ideally
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#con
                    tenteditable
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html
Multipage: http://www.whatwg.org/C#contenteditable
Complete: http://www.whatwg.org/c#contenteditable

Comment:
When tapping within a contenteditable, mobile browsers display a VKB that hogs
the screen. But what if users don't want to enter any new text?  They might
instead make a selection, copy it, drag to move it, format it, or paste in
something else.  Ideally rather than boolean, contenteditable should account
for edits that don't require text input.

Posted from: 192.100.106.9
User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.2 (KHTML, like Gecko)
Chrome/15.0.874.83 Safari/535.2

-- 
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 Thursday, 13 October 2011 18:51:25 UTC