Closed
Bug 10931
Opened 26 years ago
Closed 25 years ago
Feature: onload() and onunload() should fire for xul overlays
Categories
(Core :: XUL, enhancement, P3)
Core
XUL
Tracking
()
RESOLVED
WONTFIX
M14
People
(Reporter: hangas, Assigned: hyatt)
Details
Attachments
(1 file)
(deleted),
application/x-xpinstall
|
Details |
It would be useful to have the onload and onunload handler fire for overlay files. Sometimes it is useful to have an overlay that the main window has no knoledge of, in these cases there is no way to trigger an onload to fire for this added xul.
Assignee | ||
Updated•26 years ago
|
Target Milestone: M9 → M10
Updated•26 years ago
|
Target Milestone: M10 → M14
Comment 1•26 years ago
|
||
moving to m14
Comment 2•26 years ago
|
||
As a workaround, do this: function OnLoad() { // do whatever here } setTimeout("OnLoad();", 0);
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 3•26 years ago
|
||
good enough for me. i won't be implementing this then.
Comment 4•25 years ago
|
||
reopening: using the code below, menuElement returns null unless (at least on my machine), the delay in setTimeout is set to at least 2000. This is completely unacceptable. OnLoad() should fire on load, there should be no need for a timeout. function InitElement(ElementID) { var menuElement=document.getElementById("menu" + ElementID); } function OnLoad() { InitElement("PTBookmarks"); }
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 5•25 years ago
|
||
Assignee | ||
Comment 6•25 years ago
|
||
Not if the element hasn't been merged in yet. Besides, you can always manually add a load listener via script anyway using addEventListener. There is no need for this functionality.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•