RESOLVED FIXED 82568
textarea in Shadow DOM is not resizeable. 
https://bugs.webkit.org/show_bug.cgi?id=82568
Summary textarea in Shadow DOM is not resizeable.
Shinya Kawanaka
Reported 2012-03-28 21:04:04 PDT
Created attachment 134489 [details] Repro When <textarea> is located in Shadow DOM, it cannot be dragged to resize.
Attachments
Repro (896 bytes, text/html)
2012-03-28 21:04 PDT, Shinya Kawanaka 		no flags
Details
FYI (1.71 KB, text/plain)
2012-05-16 04:15 PDT, Takashi Sakamoto 		no flags
Details
Patch (3.05 KB, patch)
2012-05-17 22:26 PDT, Shinya Kawanaka 		rniwa: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Shinya Kawanaka
Comment 1 2012-03-28 21:04:35 PDT
Put the repro in LayoutTest/fast/dom/shadow/
Takashi Sakamoto
Comment 2 2012-05-16 04:15:36 PDT
Created attachment 142216 [details] FYI FYI.
Shinya Kawanaka
Comment 3 2012-05-17 22:26:23 PDT
Created attachment 142630 [details] Patch
Ryosuke Niwa
Comment 4 2012-05-18 11:16:06 PDT
Comment on attachment 142630 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=142630&action=review > ManualTests/drag-to-resize-textarea-in-shadow.html:4 > +<head> > +</head> Why head? > ManualTests/drag-to-resize-textarea-in-shadow.html:8 > +<p>Drag from the right-bottom cordner of the following textarea to resize.</p> > +<p>Note that Shadow DOM should be enabled to perform this test.</p> We can use eventSender for this. r- because of this.
Shinya Kawanaka
Comment 5 2012-05-20 18:07:54 PDT
> > ManualTests/drag-to-resize-textarea-in-shadow.html:8 > > +<p>Drag from the right-bottom cordner of the following textarea to resize.</p> > > +<p>Note that Shadow DOM should be enabled to perform this test.</p> > > We can use eventSender for this. r- because of this. I've tried eventSender, but I cannot reproduce the bug... Actually resize was not triggered. I didn't investigate it a lot, but many resize related bugs have ManualTest. I thought it was because eventSender cannot reproduce the bug correctly.
Shinya Kawanaka
Comment 6 2012-11-07 19:29:45 PST
This is already fixed by Bug 87342.
Note You need to log in before you can comment on or make changes to this bug.