Bug 17270

Summary: Webkit should respect the height regardless of padding for input element.
Product: WebKit Reporter: Anantha Keesara <anantha>
Component: EvangelismAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Minor CC: ap, webkit, webkit
Priority: P3    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://iskon.hr/
Attachments:
Description Flags
reduction none

Anantha Keesara
Reported 2008-02-09 23:33:25 PST
I .Steps: ----------- 1. Go to: http://iskon.hr/ II. Issue: ----------------- You would notice that text field "tražilica" is aligned down and corresponding buttons are been duplicated twice. Also when mouse hover on those button, it movies up and down. III. Observation: ----------------- For <input> elements the height is respected regardless of padding in IE6, IE7, and Opera. WebKit and Firefox expand the input greater than the height to accomodate the padding. IV. Other browsers: ------------------- This issue is not seen in IE, FF, Opera V. Nightly tested: 30110
Attachments
reduction (208 bytes, text/html)
2008-02-09 23:35 PST, Anantha Keesara 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Anantha Keesara
Comment 1 2008-02-09 23:35:14 PST
Created attachment 19028 [details] reduction
Dave Hyatt
Comment 2 2008-02-09 23:43:07 PST
We do this in strict mode.
Robert Blaut
Comment 3 2008-06-12 01:07:46 PDT
(In reply to comment #2) > We do this in strict mode. > A height of input element in attached test case is rendered identically in WebKit, Opera 9.5 and Firefox 3. Per comment #2 bug marked as an Evangelism bug.
Robert Blaut
Comment 4 2009-11-15 01:33:55 PST
I've checked the reported site in WebKit 4.0.4 (6531.21.10, r50918) and found no problem now. The issue is fixed on the page now. I close this report as resolved fixed an evangelism bug.
webkit
Comment 5 2011-08-16 21:29:24 PDT
Hi Can anyone point me to the fix/commit how this issue is resolved? -Raybits
Alexey Proskuryakov
Comment 6 2011-08-17 10:35:56 PDT
This was a site issue, not a WebKit bug. So there was no fix in WebKit, it's the site that got fixed.
Note You need to log in before you can comment on or make changes to this bug.