User-Agent: Build Identifier: The natural way to develop a chrome is: edit file(s); start mozilla with the chrome; and test. However if there is an onload() event for the main window, it is not trigger if any chrome files were modified since Mozilla was last started. Stopping Mozilla and restarting solves the problem everytime. Reproducible: Always Steps to Reproduce: 1. stop mozilla 2. edit a chrome file which has an onload() event on the window 3. start mozilla and notice that the onload event was not called 4. restart mozilla and notice that the onload now works Actual Results: The onload event is triggered Expected Results: The onload event is triggered whether the chrome files have been modified or not since the last time Mozilla was started.
14 years ago
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.