It is impossible to develop XUL apps on a Mac!



UI Design
15 years ago
12 years ago


(Reporter: Jason Henriksen, Assigned: jag (Peter Annema))


Firefox Tracking Flags

(Not tracked)



(1 attachment)



15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401

Every time there is an error with the parsing, the window takes up the entire
desktop!  There is no way to close this windows other than quitting mozilla. 
Also, dialogs that are started from inside of my xul app are in some kind of
full screen mode, despite the fact that I specify a width and height.  The XUL
error window should simply be a dialog.

Reproducible: Always

Steps to Reproduce:
1. Create a xul app that has a dialog
2. Ensure that the dialog when selected will not parse
3. Use the button to start the dialog

Actual Results:  
The error message takes over the whole screen and cannot be dismissed without
shutting down mozilla.  This turns every small error into a shutdown/restart
cycle for the browser.  There is no window bar, so I do not have the red
circular button to close with.   Because the window appears to be larger than my
monitor I have no way to grab a corner and make the window smaller.  Trying to
dismiss the parent window also fails.

Expected Results:  
Displayed the window in a dialog that has a close button and a window management
close button.  Basically, just behave in a way that allows me to dismiss the error.

This behavior also effects certain dialogs.   My full time job right now is XUL
development.  I have a nice new powerbook to work on, however due to these
errors I cannot use it.  I do not experience these errors under linux, so I'm
stuck on my old linux box until this is resolved.

I am a professional software engineer.  If there is somewhere simple you could
point me to solve the bug I'll take a look at it, but I haven't done any mozilla
dev so far.

Comment 1

15 years ago
I've also noticed that on my linux box the error window is displayed full
screen.    Linux is just has a smarter window manager that lets me see the close
button even though the window is taking up all the avaiable real estate.

Just finding a way to stick a "close" button at the top of the error window
would be enough for me to get back to work.

Comment 2

15 years ago

I posted this bug awhile ago for BeOS, Im wondering if its part of the same problem.

Comment 3

15 years ago
> 1. Create a xul app that has a dialog

please attach ("Create a New Attachment") such an app as a testcase for this bug.

if this is a Mac problem, please change hardware/OS fields appropriately.

this does not block Mozilla development.
Severity: blocker → major

Comment 4

15 years ago
Created attachment 126713 [details]
This is my application. 

 After install Tools | Reports has two buttons to show the problem

Comment 5

15 years ago
Sorry about the confusion marking as blocker.  It doesn't block the development
of mozilla but it does block my ability to use mozilla for development.

Attached is a zip file of my projects.  This will decompress into a directory
called xulapps, which should be located in your home directory.  You need to
have jslib from installed.

I use these lines in installed-chrome.txt.  Obviously, you'll need to change my
home directory name to your name.



After you've restarted mozilla you should see two applications under your tools
Agility and Reports.  Ignore Agility, it is only included because reports
depends on it.
Select the Reports tool and you should see two buttons along the bottom.  These are
two different ways that I am able to reproduce this behavior.

I'm sure you can think of any number of solutions, but quick fixes that would be
for me include a mozilla menu item that says "resize current window" or even just
"close current window"

By the way, this bug does result in loss of anything I'm doing in other mozilla
No dialogs or other windows are available while this window is expanded in this way.

Thanks for your help.  As before, if there is anything I can do to help, let me

Comment 6

14 years ago
*** Bug 210907 has been marked as a duplicate of this bug. ***
Product: Core → Mozilla Application Suite
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.