Closed Bug 1011385 Opened 11 years ago Closed 11 years ago

Button with long text or other overflow does not hide the overflow

Categories

(Core :: Layout: Form Controls, defect, P5)

x86_64
All
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: jumperchen, Unassigned)

References

Details

(Keywords: testcase, Whiteboard: [parity-IE][parity-chrome])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: Run with this example - http://jsfiddle.net/ADMxA/ Actual results: The text inside button will show over the button's edge. Expected results: The text inside button should not show over the button's edge.
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Blocks: 491180
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Whiteboard: [parity-IE][parity-chrome]
Version: 29 Branch → Trunk
Note that when I fixed bug 491180 we in fact matched the WebKit behavior after the fix... It looks like they have since changed their behavior. I'm not sure it's worth following them in the incessant flip-flopping until there's an actual spec here.
Summary: Button display wrong with long text → Button with long text allows the text to overflow
Summary: Button with long text allows the text to overflow → Button with long text or other overflow does not hide the overflow
And in particular, note that the behavior in current WebKit is weird: they're clipping some overflow but not other kinds. See testcases in bug 491180.
Fwiw, it's easy to workaround: button { overflow:hidden; }
Severity: normal → minor
Keywords: testcase
Priority: -- → P5
I believe that the current behavior of Firefox is correct. The default value of `overflow` property should be `visible`, it's useful to position some decorative elements (like arrows etc.) outside the button. IE stops to clip the button's content when `overflow:visible` is set, popular normalize.css (http://necolas.github.io/normalize.css/) uses this to fix IE's default behavior which looks like a bug. The behavior of Chrome seem to be sort of regression.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.