Closed Bug 506569 Opened 15 years ago Closed 3 years ago

Content-box on a prefpane is cutoff on Windows systems using the classic theme

Categories

(Toolkit :: Themes, defect)

1.9.1 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Gabri, Unassigned)

References

()

Details

(Keywords: regression)

Attachments

(2 files)

There is a bug under Windows systems that use the classic theme: the content-box included into a prefpane-prefwindow is cutoff and not all the options are visible by the user.

I've already found the problem and the related patch, I'll sent it soon.
Depends on: 69710
This bug was caused by the patch of bug 69710 which also included an hack to work around bug 458231. I've removed that work around because now it's useless (that bug was fixed), this patch doesn't change the firefox's behaviour about bug 69710, just fix this bug.
Attachment #390745 - Flags: review?(dao)
This should already be fixed on trunk. I don't think your patch applies.
On the trunk it's already fixed and working properly now but on the 3.5 branch this problem still exists and a user reported me it.

This patch is only for the branch (and it's a bit different from the trunk one) and I hope you'll review it because this bug makes some addons unusable.

Thanks.
Attachment #390745 - Attachment description: Proposed patch → Proposed patch (3.5 branch only)
Attachment #390745 - Flags: review?(dao) → review?(neil)
Component: Theme → Themes
Product: Firefox → Toolkit
QA Contact: theme → themes
Version: 3.5 Branch → 1.9.1 Branch
(In reply to comment #3)
> This patch is only for the branch (and it's a bit different from the trunk one)
> and I hope you'll review it because this bug makes some addons unusable.
But bug 458231 wasn't fixed on the branch, so we still need a workaround...
(not necessarily the one that we have, but we need one nonetheless)
About the workaround:
In this screenshot (testcase of bug 458231) you can see the difference between trunk (bug 458231 fixed) and the branch (with the workaround). The result is simple: the current workaround is useless (I think) and we can remove that for now (resolving this bug) and if we need another workaround we can open a new bug.

From bug 69710 comment 18: that workaround was made to avoid the change of size of the checkboxes and radios when disabled (applying a transparent text-shadow when they are enabled and a minor margin when they are disabled), see attachment 342627 [details] . That workaround resolved the problem but it created this new one (Content-box on a prefpane is cutoff), with my patch that problem (size of the checkboxes and radios) remains fixed resolving also this bug.
(In reply to comment #5)
> Created an attachment (id=390859)
> Screenshot - Workaround useless?
The workaround does not even apply to the markup that you took a screenshot of, as that only uses raw <label> elements, not checkboxes or radiogroups.

On the other hand, if I take a screenshot of SeaMonkey's Location Bar preferences, comparing latest-comm-1.9.1 and latest-comm-trunk builds, there is no difference in the rendering of the checkboxes.
(In reply to comment #6)
> (In reply to comment #5)
> > Created an attachment (id=390859) [details]
> > Screenshot - Workaround useless?
> The workaround does not even apply to the markup that you took a screenshot of,
> as that only uses raw <label> elements, not checkboxes or radiogroups.

I know that, the workaround was made ONLY to prevent the change of size
of the checkboxes and radios when disabled (attachment 342627 [details], bug 69710 comment 18) but it caused this new bug.

With the patch, as you can see, the current behaviour doesn't change and this bug is fixed.

I hope you can review it soon :)
OK, so your patch doesn't completely remove the workaround for bug 458231, it still applies it for disabled checkboxes; I assume that this helps in your case because the pane in question doesn't have any disabled checkboxes or else they get disabled at a later point where the issue does not occur?
I've just tried to insert some disabled checkboxes into the prefpane and the problem doesn't appear so I think this patch working in some cases.
Sorry, but I've tried to write a number of test cases for your patch and failed to notice any difference in behaviour. If I can't find any justification for taking this patch I'll have to ask you to get someone else to look at it.
Attachment #390745 - Flags: review?(neil)

The bug assignee didn't login in Bugzilla in the last 7 months.
:dao, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: gabri.best → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(dao+bmo)
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(dao+bmo)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: