Closed Bug 8318 Opened 27 years ago Closed 27 years ago

pop ups obliterate personal toolbar

Categories

(Core Graveyard :: Tracking, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: michaell, Assigned: waterson)

References

()

Details

Go to home.netscape.com or some other site that uses pop-ups. You may need to hit reload a couple of times to get a pop-up to appear. When it does, the personal toolbar in the main window disappears, never to be seen again (view|toolbars does not appear to be hooked up).
Assignee: don → trudelle
Component: XPApps → other
Peter, this does indeed happen on Windows although I can't reproduce the problem on Linux. This isn't really an XPApps issue but more of a Javascript and "window.open" problem. Is Hyatt still workin on that?
Assignee: trudelle → hyatt
Sounds like he may need to, reassigning.
Assignee: hyatt → danm
This probably has something to do with Dan's chrome changes. I'm assuming the wrong webshell is being targeted (the original one instead of the new popup).
Status: NEW → ASSIGNED
Better test case: executing the JS window.open("whatever", "new", "toolbar=no") will cause the problem, while an identical line with toolbar=yes will not.
Whiteboard: problem understood. fix not quite there yet.
The "chrome hidden" flag is copied between the open browser windows for the personal toolbar, which comes from an RDF datasource. The new window.open window is, yes, just another browser window. I hope this isn't an architectural problem, but I fear it is. More later.
The personal toolbar should be using a "ref" attribute rather than an "id" attribute to point to the RDF data. This will solve your problem.
Assignee: danm → waterson
Status: ASSIGNED → NEW
Whiteboard: problem understood. fix not quite there yet.
Amid worries that the attribute causing the DOM node to be hidden is being set in the wrong datasource, this bug finds a new home in the RDF camp.
Status: NEW → ASSIGNED
Target Milestone: M8
There's a workaround in the code now. While the bug itself isn't yet fixed, you can at least use the menu to get back the missing toolbar.
*** Bug 9108 has been marked as a duplicate of this bug. ***
Whiteboard: investigating
Whiteboard: investigating → fix ready to go
So what was happening here is this. The generic builder on the personal toolbar was allowing this assertion to be accepted into the local store. Wham-o, all of a sudden everyone sees it. I removed the local store from the generic builder for now: RJC will this break you in any way?
Doubt it... go for it.
Status: ASSIGNED → RESOLVED
Closed: 27 years ago
Resolution: --- → FIXED
[071699] can't get pop ups to appear, so I can't verify this one. It will have to wait until I can duplicate the problem.
Whiteboard: fix ready to go → [07301999] pop ups don't work yet
Status: RESOLVED → VERIFIED
Whiteboard: [07301999] pop ups don't work yet
although it takes the pop-up a while to close, it did not obliterate the toolbars
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.