Checkboxes and radiobuttons have too much padding

VERIFIED FIXED in mozilla0.9.1

Status

SeaMonkey
Themes
VERIFIED FIXED
17 years ago
10 years ago

People

(Reporter: Blake Ross, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

({classic, regression})

Trunk
mozilla0.9.1
x86
Windows 2000
classic, regression

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
After your landing, checkboxes and radiobuttons have far too much padding (see, 
for example, the Navigator pane in the prefs dialog).
(Reporter)

Updated

17 years ago
Keywords: mozilla0.9.1, regression
(Reporter)

Comment 1

17 years ago
This is classic-only.
Keywords: classic
(Reporter)

Comment 2

17 years ago
Ben said he had a patch for this.  Ben, can you check it in please?
Assignee: hewitt → ben
Target Milestone: --- → mozilla0.9.1

Comment 3

17 years ago
This doesn't seem like a beta stopper unless it makes the dialog unusable. 
Please reassess or provide a screen shot showing that it's unacceptable to ship
beta with this bug.
nav triage: this is not even close to being a beta or rtm stopper. Please do NOT 
add this back to the mozilla0.9.1 or mozilla0.9.2 milestones without first 
nominating nsbeta1 and giving the triage team a justfication. thanks. 
Keywords: nsbeta1-
Target Milestone: mozilla0.9.1 → Future
Wait a sec.  Bugzilla is a mozilla resource, and Ben asked for it to be put to
mozilla0.9.1 when blake filed it.  Putting a bug to 0.9.1 does not mean that it
needs to be appropriate for your beta; If you want to retriage Ben's bugs, I
guess that's your right, but I don't think it's appropriate for you insinuate
that mozilla0.9.1 == nsbeta1.

If Ben has a fix for this bug, why won't you let it get checked in?

(Ben: if you can't justify keeping this in the Mozilla 0.9.1 milestone, please
reassign to me, and we'll talk about digging your patch out.)


Target Milestone: Future → mozilla0.9.1
(Reporter)

Comment 6

17 years ago
Yes, the mozilla0.9.1 designation was a reminder to check the simple patch in.  
Do whatever you want with Ben's bugs, but don't accuse me (twice) of nominating 
this for any beta (which is the explicit purpose of the 'nsbeta1' keyword -- 
did anyone notice its conspicious absence?).  I don't intend on justifying bugs 
for nsbeta1 when I clearly didn't nominate them for it.
Fixed. 
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
for Netscape contributors, in addition to usual mozilla rules, mozilla0.9.1 ==
nsbeta1 stopppers. for non-Netscape contributors, only the mozilla tree rules
apply. 

my comment meant: Ben, do not add this to the m0.9.1 milestone and non-Ben
people, please do not set the target milestone on Ben's bugs to mozilla0.9.1.
(that's ben's and my prerogative). 

thanks, Vishy 

Updated

17 years ago
Status: RESOLVED → VERIFIED

Comment 9

17 years ago
Verified on windows 98 (commercial build: 2001-05-30-09-trunk).
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.