Closed Bug 49363 Opened 25 years ago Closed 25 years ago

Component field collapes when displayed local

Categories

(Core :: Layout: Form Controls, defect, P3)

Sun
Solaris
defect

Tracking

()

VERIFIED WORKSFORME
Future

People

(Reporter: axel, Assigned: rods)

References

()

Details

When starting the build from today (CVS, optim, no debug) locally, the field for the components on the bugzilla query page displays, but then collapses. Running the same bin remotely on another machine, it is ok. Tips: shmat failed on starting the local one: *** Registering sample JS components Gdk-WARNING **: shmat failed! Gdk-WARNING **: shmat failed! WEBSHELL+ = 1 And I get some messages locally, that I don't get remotely: Document http://bugzilla.mozilla.org/ loaded successfully nsWindow::DispatchDeactivateEvent 8a9510 Document http://bugzilla.mozilla.org/query.cgi loaded successfully nsWindow::DispatchActivateEvent 2d98e8 nsWindow::DispatchDeactivateEvent 8a9510 nsWindow::DispatchActivateEvent 2d98e8 Possible DOM Error: .name, .nodeName or .tagName requested on a namespace element/attribute with the qulaified name 'xul:thumb', is this OK? Possible DOM Error: .name, .nodeName or .tagName requested on a namespace element/attribute with the qulaified name 'xul:slider', is this OK? Document http://bugzilla.mozilla.org/describecomponents.cgi loaded successfully nsWindow::DispatchDeactivateEvent 7d6228 nsWindow::DispatchActivateEvent 2d98e8 Document http://bugzilla.mozilla.org/query.cgi loaded successfully nsWindow::DispatchDeactivateEvent 7a8d78 Axel
Is this reproducable?
marking as future for now
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Hi rod, I could reproduce it the day I filed the bug, but the same binary works today. This must have been some weirdness between me, mozilla and solaris. Huh? yeah. I don't have more than worksforme. If it comes back to life, I'll reopen. Axel
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
sounds good
Updating QA contact.
QA Contact: ckritzer → bsharma
marking verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.