133371 2014-05-29 00:47:59 -0700 Element.isContentEditable should return true in hidden elements 2014-06-06 14:03:47 -0700 1 1 1 Unclassified WebKit HTML Editing 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 pkoszulinski webkit-unassigned aleksander ap enrica kling koivisto man.zhong rniwa oldest_to_newest 1012368 0 pkoszulinski 2014-05-29 00:47:59 -0700 Identical issue was reported for Blink: https://code.google.com/p/chromium/issues/detail?id=313082 It was confirmed after Anne van Kesteren commented that spec does not suggest that isContentEditable depends on synchronous style resolution. > Example URL: > http://jsfiddle.net/kNNzK/5/ > > Steps to reproduce the problem: > 1. Create a hidden element > 2. Add a child element with contenteditable="true" > 3. Query child element isContentEditable > > What is the expected behavior? > Return true > > What went wrong? > Returned false Reproduced it on Safari 7.0.3. 1012369 1 pkoszulinski 2014-05-29 00:48:25 -0700 This issue causes CKEditor to initialize in read only mode if initialization happened in hidden container. This is a common case for SPAs. Of course it can be workaround by getAttribute('contenteditable') and DOM traversing, but it's hard to control whether editor is visible when reading isContentEditable. And switching to deoptimised version is not good option, because we use this check very often. Related ticket: http://dev.ckeditor.com/ticket/9814 1013308 2 man.zhong 2014-06-04 07:34:23 -0700 checked on WebKit-EFL, can't repro this issue. 1013767 3 rniwa 2014-06-06 02:22:16 -0700 Doesn't reproduce on the latest nightly builds of WebKit either. It's probably fixed by http://trac.webkit.org/changeset/160966. 1013820 4 pkoszulinski 2014-06-06 11:13:43 -0700 In which version of Safari that commit will be included? I can still reproduce this issue on Safari 7.0.4. 1013829 5 ap 2014-06-06 11:40:36 -0700 Please test with a nightly build from <http://nightly.webkit.org>. We never discuss future Apple releases. 1013845 6 rniwa 2014-06-06 14:03:47 -0700 Confirmed that this bug has been fixed by r160966.