Bug 117888 - REGRESSION(r143270-r143346): non-disabled textarea can't be selected or edited
Summary: REGRESSION(r143270-r143346): non-disabled textarea can't be selected or edited
Status: RESOLVED DUPLICATE of bug 117666
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.8
: P1 Normal
Assignee: Nobody
URL: http://jwysiwyg.github.io/jwysiwyg/he...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-21 12:17 PDT by Parker Morse
Modified: 2013-06-24 15:58 PDT (History)
0 users

See Also:


Attachments
HTML reduction showing the problem (878 bytes, text/html)
2013-06-21 12:17 PDT, Parker Morse
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Parker Morse 2013-06-21 12:17:25 PDT
Created attachment 205207 [details]
HTML reduction showing the problem

The jWYSIWYG rich-text editor for jQuery stores HTML in a textarea element, and toggles the `display` CSS of that element to allow users to edit raw HTML if they wish to tweak what jWYSIWYG produces.

We found that textarea can't be edited in the current stable version of Chrome (27.0.1453.116, specifically) but worked fine in previous versions (e.g. 26.) Safari 6.0.5 works fine as well. I expect to be able to click in the textarea and have it receive focus, and for the text inside to be selectable and editable; instead, none of that is the case, and clicks in the textarea are (apparently) ignored.

I verified that the problem existed in r151773, the nightly for June 20, 2013, then ran a binary search on the nightly builds to narrow the regression down from r143270 (the latest build I could find which doesn't show the problem) to r143346 (the oldest build which does show the problem). 

The jWYSIWYG example page linked above demonstrates the issue. I am attaching a reduction starting from that page.
Comment 1 Parker Morse 2013-06-21 12:28:07 PDT
Looks like this also got reported against Chromium, and they have a patch: https://code.google.com/p/chromium/issues/detail?id=246738
Comment 2 Alexey Proskuryakov 2013-06-24 15:58:16 PDT

*** This bug has been marked as a duplicate of bug 117666 ***