117666 2013-06-14 17:32:35 -0700 REGRESSION (r143299): Cannot edit text after clicking 'View source code' button on jWYSIWYG 2024-07-24 00:02:19 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All All NEW http://akzhan.github.io/jwysiwyg/help/examples/02-full.html BlinkMergeCandidate, InRadar P2 Normal --- 110172 1 aestes webkit-unassigned ahmad.saleem792 karlcow pmorse rniwa webkit-bug-importer oldest_to_newest 900714 0 aestes 2013-06-14 17:32:35 -0700 After <http://trac.webkit.org/changeset/143299>, you can no longer edit text on in source code mode on the jWYSIWYG editor. This was first reported to the Chromium project: https://code.google.com/p/chromium/issues/detail?id=246738 900716 1 aestes 2013-06-14 17:34:04 -0700 <rdar://problem/14163133> 903109 2 ap 2013-06-24 15:58:16 -0700 *** Bug 117888 has been marked as a duplicate of this bug. *** 903110 3 ap 2013-06-24 15:58:44 -0700 A fix was landed in Blink. 903114 4 aestes 2013-06-24 16:05:23 -0700 (In reply to comment #3) > A fix was landed in Blink. Blink's fix was just to roll out r143299. I don't want to do that before taking the time to investigate the issue. We might be able to fix it without regressing webkit.org/b/110172. 1892866 5 rniwa 2022-08-21 19:20:56 -0700 https://github.com/akzhan/jwysiwyg doesn't exist anymore. 1892867 6 rniwa 2022-08-21 19:21:27 -0700 I guess the latest website is https://github.com/cmelbye/jwysiwyg 1902187 7 ahmad.saleem792 2022-09-29 14:58:16 -0700 Chrome Commit was trying to modify DOMWindow.cpp and this bit: https://github.com/WebKit/WebKit/blob/64f843f962fd4b62b95fb3c3c53127b6f526fbcd/Source/WebCore/page/DOMWindow.cpp#L1001 via this commit: https://src.chromium.org/viewvc/blink?view=revision&revision=152395 While on Chrome Bug, it seems that the bug was back in Chrome 64 onward.. https://bugs.chromium.org/p/chromium/issues/detail?id=246738#c17 Do we want this fix? Thanks! 2047954 8 karlcow 2024-07-24 00:02:19 -0700 The project pointed by Ryosuke has not been updated for 14 years. I wonder if there are still people using it. Or if there is a test case to reproduce the issue.