Textareas should respond to input from the scroll wheel/track pad but do not in ToT. Scrolling over a textarea does not move the text at all. Also, scrolling past a textarea in a page in shipping Safari scrolls the page up to the textarea, scrolls the content in the textarea, then when it reaches the end of the content in the textarea, it continues scrolling the rest of the page - this does not happen in ToT, the textarea simply scrolls by.
Testcase in a minute.
Created attachment 11108 [details]
Filed as <rdar://problem/4808089>
*** Bug 11578 has been marked as a duplicate of this bug. ***
Any fix for this yet?
This seems to have regressed even further since I first reported it. Originally, scroll wheel input was ignored, but the scroll bar/arrows on the textbox worked correctly. Now the scroll bar/arrows are ignored as if they aren't there, the only way to shift what content is displayed in a textarea is to highlight and select up/down.
(In reply to comment #5)
> Now the scroll bar/arrows are ignored as if they
> aren't there, the only way to shift what content is displayed in a textarea is
> to highlight and select up/down.
Filed bug 11632 on scrollbars not responding to events since r17770.
This appears to be because the code in RenderObject::scroll is not finding the RenderTextControl's internal m_div's layer, but rather is just seeing that RenderTextControl itself has no layer and giving up without scrolling.
I'm not sure what the right fix is here - it seems like overriding |scroll| on RenderTextControl might be safest?
Adele, this looks like a shadow DOM issue.
Overriding sounds pretty good. I did something similar for the impl of scrollLeft and scrollTop etc.
I'm rewriting the shadow DOM for this control right now. I'll work on this after I've checked that in.
Created attachment 11827 [details]
patch (what I had)
Hi Adele, in case it helps here's what I had for this.
Comment on attachment 11827 [details]
patch (what I had)
actually that looks nice and easy to merge with what I have.
Committed revision 18253.
*** Bug 10747 has been marked as a duplicate of this bug. ***