Bug 94102 - Textarea scaled by transform does not respect new dimensions for scrolling
Summary: Textarea scaled by transform does not respect new dimensions for scrolling
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 420+
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2012-08-15 06:42 PDT by Dan Peddle
Modified: 2018-10-15 08:04 PDT (History)
5 users (show)

See Also:


Attachments
Testcase for showing problem at 70%, 100% and 120%. (902 bytes, text/html)
2012-08-15 06:52 PDT, Dan Peddle
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Peddle 2012-08-15 06:42:15 PDT
Example CSS and html: http://jsfiddle.net/dazzled/ydSSf/3/

Overview:

Textareas scaled by transform do not reflect new dimensions for scrolls

Steps to Reproduce: 

Scale textarea with transform. add new lines at bottom of textarea and observe caret position.

Actual Results: 

Caret in downscaled textarea will go outside visible textarea. Caret in upscaled textarea will not go outside of box, but the textarea will start scrolling before reaching the end or beginning of visible textarea when adding text or using cursors.

Expected Results: 

Textarea will behave as 100% version in every regard.
Comment 1 Dan Peddle 2012-08-15 06:52:24 PDT
Created attachment 158562 [details]
Testcase for showing problem at 70%, 100% and 120%.
Comment 2 Mihai Balan 2012-08-16 04:30:28 PDT
To be more specific, the bug manifests when using the arrow keys to scroll through the textarea:
* when scaled at < 100%, the cursor will move past the visible area before scrolling occurs
* when scaled at > 100%, scrolling will occur before reaching the limits of the visible area
Comment 3 Allan Sandfeld Jensen 2012-09-04 01:38:21 PDT
Confirmed. Only caret navigation seems to be affected though.
Comment 4 Dan Peddle 2012-09-05 01:33:32 PDT
Reported and confirmed to Chromium team. 

http://code.google.com/p/chromium/issues/detail?id=146313#c2
Comment 5 Sukolsak Sakshuwong 2013-04-13 13:15:59 PDT
This bug was fixed in r140202 <http://trac.webkit.org/changeset/140202>
Comment 6 Dan Peddle 2018-10-15 08:03:24 PDT
this looks fixed!
Comment 7 Radar WebKit Bug Importer 2018-10-15 08:04:26 PDT
<rdar://problem/45271233>