Bug 8362 - Scrollbars in <textarea> should gracefully shrink if they don't fit.
Summary: Scrollbars in <textarea> should gracefully shrink if they don't fit.
Status: RESOLVED DUPLICATE of bug 5005
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 417.x
Hardware: Mac OS X 10.4
: P4 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-13 02:11 PDT by Mark Slater
Modified: 2006-04-13 04:06 PDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Slater 2006-04-13 02:11:32 PDT
When the user types enough text into a <textarea> form control, it automatically adds a vertical and/or horizontal scrollbar. Sometimes, depending on the size of the page font, the size of the control doesn't allow the control to draw itself, so it appears as a disabled scrollbar. Since MacOS X has several scrollbar sizes, it would be nice if the size of the textarea scrollbar were reduced, when necessary, to allow the control to be rendered and used.

The following HTML demonstrates this:

<html>
<head><title>TextArea Scrollbar demonstration</title></head>
<body>
<p>Use the Cmd-'-' and Cmd-'+' to make the text larger and smaller. If the font is large enough,
the scrollbar is rendered and usable. If the font gets too small, the control is disabled.</p>
<form>
<textarea cols=30 rows=5 wrap=virtual>
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. 
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. 
Excepteur sint aliquam is nostrud exercitation ullam occaecat cupidatat non proident.
</textarea>
</form>
</html>
Comment 1 mitz 2006-04-13 04:05:37 PDT

*** This bug has been marked as a duplicate of 3911 ***
Comment 2 mitz 2006-04-13 04:06:51 PDT
Oops

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