[Webkit-unassigned] [Bug 58959] New: "contenteditable" elements should not need to be in the DOM tree
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Apr 19 20:14:45 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=58959
Summary: "contenteditable" elements should not need to be in
the DOM tree
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: joepeck at webkit.org
Created an attachment (id=90296)
--> (https://bugs.webkit.org/attachment.cgi?id=90296&action=review)
[TEST] Test case for contenteditable elements not in the DOM or display:none
My interpretation of the spec is that an element can have isContentEditable
as true, even if it is not attached to the DOM tree, but just a created
elements with contentEditable="true".
I attached a test case which works in Firefox (3 passes) but has only 1 pass in WebKit.
If the description of "editing context" is ambiguous I think we should get
clarification in the spec.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list