Closed Bug 556645 Opened 10 years ago Closed 9 years ago

Extra resizer on some XUL dialogs

Categories

(Core :: XUL, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: ehsan, Assigned: enndeakin)

References

Details

(Keywords: dev-doc-complete, regression)

Attachments

(2 files)

Attached image Screenshot
See the attachment for a sample of the problem.  I _think_ that this is a regression from the textarea resizer addition.
It's a regression from setting -moz-appearance: resizer on resizers on Mac in bug 510333.
Blocks: 510333
No longer blocks: 167951
Markus, so the Mac widget code is applying the native resizer by default, and the <resizer> in the cookies dialog is only needed for non-Mac?

Maybe we need to add a variation (say, type="window") that is hidden on Mac.
(In reply to comment #2)
> Markus, so the Mac widget code is applying the native resizer by default, and
> the <resizer> in the cookies dialog is only needed for non-Mac?

Correct.

> Maybe we need to add a variation (say, type="window") that is hidden on Mac.

Or we hide it by default and set class="textbox-resizer" on those inside textboxes and only show those.
(In reply to comment #3)
> Or we hide it by default and set class="textbox-resizer" on those inside
> textboxes and only show those.

That wouldn't work for any other usage of <resizer> in a window.
Then maybe resizer[element] { ... }? I guess that still wouldn't work for resizers in panels... OK, type="window" is good.
Attached patch like soSplinter Review
Assignee: nobody → enndeakin
Status: NEW → ASSIGNED
Attachment #456074 - Flags: review?(dao)
Comment on attachment 456074 [details] [diff] [review]
like so

Not good for cross-platform development, but I don't have a better suggestion.
Attachment #456074 - Flags: review?(dao) → review+
http://hg.mozilla.org/mozilla-central/rev/7c7f74ecf1c6
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Documented: https://developer.mozilla.org/en/XUL/resizer

Let me know if this is wrong in any way.
You need to log in before you can comment on or make changes to this bug.