RESOLVED FIXED16540
text control does not line up with image
https://bugs.webkit.org/show_bug.cgi?id=16540
Summary text control does not line up with image
scroggo
Reported 2007-12-20 13:29:18 PST
At the upper right corner of the page, click on the white space next to the magnifying glass. A text control takes focus, but it does not line up with the white space. In Firefox it behaves as expected. I am not sure of the version, but we sunc to webkit on November 16, and the SVN number is 27453, and I am using it to run Safari 2.
Attachments
Partial offline reduction (.tar.gz) (1.84 KB, application/x-gzip)
2007-12-21 13:31 PST, David Kilzer (:ddkilzer)
no flags
test case (251 bytes, text/html)
2008-03-06 05:04 PST, Robert Blaut
no flags
mitz
Comment 1 2007-12-20 17:28:51 PST
Looks the same in Firefox 3.
David Kilzer (:ddkilzer)
Comment 2 2007-12-21 11:40:28 PST
Hitting the tab key to highlight elements on the page leads to some strange highlighting when the "S60" and "S60.com" tabs are highlighted. FIled Bug 16560.
David Kilzer (:ddkilzer)
Comment 3 2007-12-21 13:31:45 PST
Created attachment 18039 [details] Partial offline reduction (.tar.gz) A partial reduction of the original page. The input text field is still mispositioned on Safari 3/WebKit nightlies and Firefox 3.0b3 previews, but is positioned as expected on Firefox 2.
Robert Blaut
Comment 4 2008-03-06 05:04:43 PST
Created attachment 19568 [details] test case
Robert Blaut
Comment 5 2008-03-06 05:09:25 PST
The test clearly shows that margin-bottom:8px causes input box rendered higher in Firefox 2. It is probably bug in this browser.
Robert Blaut
Comment 6 2008-03-06 05:23:28 PST
(In reply to comment #5) > The test clearly shows that margin-bottom:8px causes input box rendered higher > in Firefox 2. It is probably bug in this browser. Indeed. margin of inline-blocks (input element) shouldn't cause repositioning of an element however its margin has influence on margin of parent block element. An evangelism bug.
Robert Blaut
Comment 7 2008-07-17 01:54:12 PDT
The site is fixed now. The described issue isn't visible any more. Tested in Firefox and WebKit r35203. Closing as fixed.
Note You need to log in before you can comment on or make changes to this bug.