Closed
Bug 141863
Opened 24 years ago
Closed 24 years ago
Pref to prevent hiding status bar on all windows
Categories
(SeaMonkey :: UI Design, enhancement, P2)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0.1
People
(Reporter: security-bugs, Assigned: caillon)
References
Details
(Whiteboard: [adt2 rtm])
Attachments
(1 file)
|
12.40 KB,
patch
|
caillon
:
review+
caillon
:
superreview+
chofmann
:
approval+
|
Details | Diff | Splinter Review |
We would like a pref which will force all browser windows to have a status bar
(the one along the bottom of the window) regradless of the window parameters
specified by scripts.
Comment 3•24 years ago
|
||
Nav triage team needs info: Why? What is the benefit to customers/users?
Severity: normal → enhancement
Whiteboard: [need info]
Comment 4•24 years ago
|
||
It is a mechanism to thwart a form of chrome-spoofing. As long as some part of
the chrome can not be overridden by scripts, chrome-spoofing is trickier. It
specifically prevents spoofing of the lock icon.
Comment 5•24 years ago
|
||
See also bug 143886, pref to ignore window.open flags.
Comment 6•24 years ago
|
||
Malicious sites can use https, so I don't think it really matters if sites can
spoof the lock icon. People who find this pref wouldn't give their credit card
number to a random site just because it claims to be secure.
Comment 7•24 years ago
|
||
A malicious site can use HTTPS, but if site X is trying to spoof site Y, the
lock gives access to the real certificate viewer (not a spoofed one), and the
certificate will identify the actual site (site X). If I'm able to show a fake
lock icon, I can take you to a fake cert viewer, thereby preventing true
identification of the site.
Comment 8•24 years ago
|
||
If you want to keep sites from spoofing other sites, keep the location bar
visible, not the status bar.
Comment 9•24 years ago
|
||
nsbeta1- per Nav triage team. Nice to have, but too late for MachV, will
consider for future release.
| Reporter | ||
Comment 10•24 years ago
|
||
OK, I'll take it.
nsbeta1-
Before you renominate, please query bugs marked nsbeta1+ keyword with [ADT# RTM]
in status whiteboard (where # is a number between 1 and 3) and make sure that
this bug is at least as important as those.
Comment 12•24 years ago
|
||
Dupe of bug 107949 which is more general?
pi
| Assignee | ||
Comment 13•24 years ago
|
||
This will be fixed on the trunk by bug 107949, but this bug will be tracking the
feature as it goes on the branch which will include only a fix for preventing
the statusbar from being hidden. Moving over nsbeta1+ and keywords from bug
107949, and re-assigning to self.
Assignee: mstoltz → caillon
Depends on: 107949
Priority: -- → P2
Whiteboard: [adt2 rtm]
Target Milestone: mozilla1.2alpha → mozilla1.0.1
| Assignee | ||
Comment 14•24 years ago
|
||
Refactored code from bug 107949.
| Assignee | ||
Comment 15•24 years ago
|
||
Comment on attachment 86324 [details] [diff] [review]
Patch v1.0
Copying over r=danm, sr=jag from the patch in bug 107949
Attachment #86324 -
Flags: superreview+
Attachment #86324 -
Flags: review+
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 16•24 years ago
|
||
adding adt1.0.1+ for adt approval for checkin to the branch. Please get drivers
approval before checking in.
Comment 17•24 years ago
|
||
Comment on attachment 86324 [details] [diff] [review]
Patch v1.0
a=chofmann for 1.0.1 add the fixed1.0.1 keyword and remove mozilla1.0.1+ after
checking in.
Attachment #86324 -
Flags: approval+
Updated•24 years ago
|
Keywords: mozilla1.0.1 → mozilla1.0.1+
| Assignee | ||
Comment 18•24 years ago
|
||
Fixed on branch.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Keywords: mozilla1.0.1+ → fixed1.0.1
Resolution: --- → FIXED
Comment 19•24 years ago
|
||
VERIFIED Fixed on 20020627 branch builds. since this fix doesn't explicitly
exist on trunk builds I'll just set it as verified fixed as well.
Status: RESOLVED → VERIFIED
Updated•24 years ago
|
Keywords: fixed1.0.1 → verified1.0.1
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•