Closed
Bug 346367
Opened 18 years ago
Closed 17 years ago
CSS outline property moves textarea by 1px
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: timwi, Assigned: roc)
References
Details
(Keywords: testcase)
Attachments
(1 file)
(deleted),
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 The CSS specification clearly states about the 'outline' property that: Outlines do not take up space. However, the following attachment demonstrates that for textarea elements, the 'outline' property changes the width of the area usable by the contained text. In some cases this can cause the text to word-wrap differently. Reproducible: Always
P.S. The bug occurs only if the textarea's border-width is set to 2px (which is the default). Setting border-width to 1px or 3px makes the bug go away.
Comment 3•18 years ago
|
||
Sounds like a rounding issue (which I can't reproduce on Linux, fwiw). Should be revisited once bug 177805 lands.
Assignee: nobody → roc
Component: Layout: Form Controls → Layout: View Rendering
Depends on: pixels
QA Contact: layout.form-controls → ian
Comment 4•18 years ago
|
||
I think this is already fixed somehow on trunk. I can see the bug in a 1.8.1 build with the testcase, but not in current trunk build.
Summary: CSS outline properly moves textarea by 1px → CSS outline property moves textarea by 1px
Confirming comment 4. I see his in FF 2.0.0.1 (winXP), but not with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070204 Minefield/3.0a2pre (pre bug 17705 landing)
> (pre bug 17705 landing) (pre bug 177805 landing)
Appears to work in Firefox 3 Beta 5. Closing.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Flags: in-testsuite?
Updated•6 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•