In M17 with prefs set for codebase principals: pref("signed.applets.codebase_principal_support", true); and using UniversalBrowserWrite permission, setting the visible property of the following objects does not stick nor does it change the actual visibility of the window chrome piece: window.directories (*) window.locationbar window.menubar window.personalbar window.scrollbars window.statusbar window.toolbar All but (*) were available in NN4 with signed scripts or codebase principles turned on. With codebase principles turned on, no exceptions are thrown.
Reassigning to DOM for further analysis. I don't think the security manager is the problem here. Are these even supposed to work as before? Do they work on the fly, or only when a new window is opened?
Assignee: mstoltz → jst
Status: UNCONFIRMED → NEW
Component: Security: General → DOM Level 0
Ever confirmed: true
QA Contact: czhang → desale
Target Milestone: --- → M19
Reassigning to Dan who's working in this area...
Yes, they're supposed to work on the fly. The problem is, while Travis was pushing around braces and indentation in nsBarProps.cpp, he also changed some code for some reason. Reverting this odd line (line 247 of nsBarProps.cpp rev 1.8) chromeFlags |= ~aChromeFlag; to its original chromeFlags &= ~aChromeFlag; fixes this problem. (For the most part -- the actual implementation of certain properties (menubar.visible on Windows, for instance) is broken.) But this is a safe change. We should probably fix it. Nominating rtm.
Status: NEW → ASSIGNED
rtm+ need info. one-liner to fix regression, Nav 4.x compatibility issue.
Priority: P3 → P2
Whiteboard: fix in hand → [rtm+ need info] fix in hand
Yep, looks like a no-brainer. sr=waterson.
Fine with me, r=jst
PDT marking [rtm++]
Whiteboard: [rtm+] → [rtm++]
checked in, trunk & netscape rtm branch
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Verified with 2000-10-16-09.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.