Closed
Bug 31066
Opened 25 years ago
Closed 24 years ago
Reloading Chrome Should do onReload and not actually reload
Categories
(Core :: XUL, defect, P3)
Tracking
()
VERIFIED
WONTFIX
People
(Reporter: travis, Assigned: danm.moz)
References
Details
When there is a window of the same name that already exists for a window.open, we should not reload that chrome, but rather should just bring that window to the foreground and execute a js OnReload or something like that.
Comment 2•24 years ago
|
||
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
I don't quite remember what this bug refers to. I gather we're talking about JS like open("chrome://thing","name","chrome") executing with a window already open with that name. And thinking that it should not reload the chrome URL; just the content. That would be nice and more like Navigator, but requires treating chrome content differently from non-chrome content. It would probably also require special hooks in everyone's chrome, allowing it to be reverted to a pristine state, ready for new content. I'm thinking this will cause lots of problems, and wanting to not do it.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•