Bug 17759 - font-family/font-size is causing misalignment issue
Summary: font-family/font-size is causing misalignment issue
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
Keywords: HasReduction
Depends on:
Reported: 2008-03-10 19:15 PDT by jasneet
Modified: 2008-05-15 10:52 PDT (History)
2 users (show)

See Also:

reduction (356 bytes, text/html)
2008-03-10 19:15 PDT, jasneet
no flags Details
Correct way to fix this (558 bytes, text/html)
2008-05-15 10:51 PDT, David Kilzer (:ddkilzer)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description jasneet 2008-03-10 19:15:23 PDT
I Steps:
Go to the attached reduction

II Issue:
the checkbox and checkbox option should be next to each other. Instead check box is on the end of line and check box option is on start of next line.

III Conclusion:
Case 1 - When font-family is removed: Only IE render correctly.
Case 2 - When font-size is removed: Only FF render correctly.
Case 3 - When both font-family and font-size are removed: Only Safari render it correctly.(render similar to case 2)

IV Other browsers:
IE7: ok
FF2: ok
Opera: not ok

V Nightly tested: 30881
Comment 1 jasneet 2008-03-10 19:15:52 PDT
Created attachment 19652 [details]
Comment 2 David Kilzer (:ddkilzer) 2008-05-15 10:51:46 PDT
Created attachment 21168 [details]
Correct way to fix this

I don't think this is a bug.  Different browsers are going to render checkboxes (and the space around them) differently.  If you always want the checkbox next to the text, use a "white-space: nowrap;" style around each checkbox and label text.  Then it should work for every web browser (that supports basic CSS styles).

If you want to be more user-friendly, add id attributes to each <input> tag and use <label for=""></label> tags around the text for each checkbox to make the click area bigger.
Comment 3 David Kilzer (:ddkilzer) 2008-05-15 10:52:58 PDT
Marking bug as RESOLVED/INVALID per Comment #2.