Bug 117666 - REGRESSION (r143299): Cannot edit text after clicking 'View source code' button on jWYSIWYG
Summary: REGRESSION (r143299): Cannot edit text after clicking 'View source code' butt...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://akzhan.github.io/jwysiwyg/help...
Keywords: BlinkMergeCandidate, InRadar
: 117888 (view as bug list)
Depends on: 110172
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-14 17:32 PDT by Andy Estes
Modified: 2022-09-29 14:58 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Estes 2013-06-14 17:32:35 PDT
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
Comment 1 Andy Estes 2013-06-14 17:34:04 PDT
<rdar://problem/14163133>
Comment 2 Alexey Proskuryakov 2013-06-24 15:58:16 PDT
*** Bug 117888 has been marked as a duplicate of this bug. ***
Comment 3 Alexey Proskuryakov 2013-06-24 15:58:44 PDT
A fix was landed in Blink.
Comment 4 Andy Estes 2013-06-24 16:05:23 PDT
(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.
Comment 5 Ryosuke Niwa 2022-08-21 19:20:56 PDT
https://github.com/akzhan/jwysiwyg doesn't exist anymore.
Comment 6 Ryosuke Niwa 2022-08-21 19:21:27 PDT
I guess the latest website is https://github.com/cmelbye/jwysiwyg
Comment 7 Ahmad Saleem 2022-09-29 14:58:16 PDT
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!