Bug 58959

Summary:

"contenteditable" elements should not need to be in the DOM tree

Product:

WebKit

Reporter:

Joseph Pecoraro <joepeck>

Component:

WebCore Misc.

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

ap, enrica, joepeck, stumpfmozessm

Priority:

Version:

528+ (Nightly build)

Hardware:

OS:

OS X 10.5

Attachments:

Description	Flags
[TEST] Test case for contenteditable elements not in the DOM or display:none	none

Joseph Pecoraro

Reported 2011-04-19 20:14:45 PDT

Created attachment 90296 [details] [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.

Attachments
[TEST] Test case for contenteditable elements not in the DOM or display:none (1.32 KB, text/html) 2011-04-19 20:14 PDT, Joseph Pecoraro	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Mozes Stumpf

Comment 1 2024-11-26 23:41:21 PST

Is there any chance of fixing this bug?

Note You need to log in before you can comment on or make changes to this bug.