Closed Bug 42210 Opened 25 years ago Closed 25 years ago

Dialogs open extremely large and buttons are not accessible

Categories

(Core :: DOM: Editor, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: rubydoo123, Assigned: cmanske)

Details

(Whiteboard: [nsbeta2+][dogfood-])

using the build from 6/12 on win98: 1. selected insert link (tried other dialog boxes too, and the same thing happpens) 2. dialog opened -- it stretched the width of the screen -- the ok and cancel buttons were not accessible
Keywords: dogfood, nsbeta2
forgot to set the milestone
Target Milestone: --- → M16
Not again! This is usually a XUL box problem.
Is this all dialogs? [NEED INFO]
Whiteboard: [NEED INFO]
it certainly happens with link, and image dialogs I didn't check all 22+ dialog boxes, bu these 2 alone make it impossible to use
Putting on [nsbeta2+][dogfood-] radar. Does not need a fix ASAP for daily work, but we should fix this for beta2.
Whiteboard: [NEED INFO] → [nsbeta2+][dogfood-]
Only dialogs with the "More/Fewer Properties" button should be affected, which currently is Link and Page Properties. Image dialog should use this, but currently modifies "display" attribute instead of "visibility" because of other problems. Beth: You see the problem in the Image dialog? I don't.
Status: NEW → ASSIGNED
hmm, so applying links and inserting images is not important? If you use the app and need to insert links or images I would think it was important. Currently, you access the dialogs, but you can't insert those elements -- that smells like dogfood to me.
Whiteboard: [nsbeta2+][dogfood-] → [nsbeta2+]
[dogfood-], hit return.
Whiteboard: [nsbeta2+] → [nsbeta2+][dogfood-]
totally disagree with your assessement, it's apparent that Composer is not being used for daily dogfood
checked in. Simple fix: we should use "visibility: collapsed", not "display: none" when we want to hide dialog content. The fact that "display: none" isn't working is really a bug, but I'll file that at some later time, since it should never be used in XUL anymore.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified in 6/14 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.