This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14455 - 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
Summary: When tapping within a contenteditable, mobile browsers display a VKB that hog...
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - HTML Editing APIs (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Aryeh Gregor
QA Contact: HTML Editing APIs spec bugbot
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-13 18:51 UTC by contributor
Modified: 2011-10-24 14:56 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-10-13 18:51:23 UTC 
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
Comment 1 Aryeh Gregor 2011-10-24 14:56:02 UTC 
This doesn't seem like a strong enough use-case to justify a new mode for contenteditable at this point.  There are lots of other things that are much more important.  Also, the mobile browser could be smart enough to not pop up the virtual keyboard if you're making a selection, dragging something, etc., and we don't need to change the spec for that.

Thanks for your suggestion, though.  Please reopen if you think there's something I've missed.