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 9380 - If contenteditable is true, this *should* mean that the *content* of the element is editable, not the element itself. For example, if the user selects "mytext" in <div contenteditable=true>mytext</div>, and then invokes execCommand('bold'), this should wr
Summary: If contenteditable is true, this *should* mean that the *content* of the elem...
Status: CLOSED DUPLICATE of bug 9379
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-31 21:59 UTC by contributor
Modified: 2010-10-04 14:57 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-31 21:59:04 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#contenteditable

Comment:
If contenteditable is true, this *should* mean that the *content* of the
element is editable, not the element itself. For example, if the user selects
"mytext" in <div contenteditable=true>mytext</div>, and then invokes
execCommand('bold'), this should wrap the selection in <b> or <strong> or
<span style='font-weight: bold'> tags, but it should *not* alter the div
element to be <div contenteditable=true style='font-weight: bold'>

Posted from: 64.253.149.226
Comment 1 Michael[tm] Smith 2010-04-01 09:44:56 UTC 

*** This bug has been marked as a duplicate of bug 9379 ***