Closed Bug 102260 Opened 23 years ago Closed 16 years ago

premiermembers.org - hiermenu 3 not working.

Categories

(Tech Evangelism Graveyard :: English US, defect, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jud, Unassigned)

References

()

Details

(Whiteboard: [USERAGENT] [hiermenu][bank])

Attachments

(2 files)

problem:
mouse hovering over "toolbar" items doesn't show sub menu.

steps to repro:
1. visit said URL
2. hover mouse over the items (Home, Investements, Mortgage, etc) in the purple
"toolbar" near the top of the page.
3. notices that right underneath the toolbar, nothing shows up.

expected behavior:
sub menus underneath the purlple toolbar display when you hover over the toolbar
items.

This works in 4.x and IE
Severity: normal → critical
Keywords: 4xp, mozilla0.9.5
Summary: JS menu not working. → premiermembers.org - JS menu not working.
process question. the URL is in the URL field, why did you add it to the Summary
field too?
Since the buglist results from queries do not show the url, it is sometimes hard
to find duplicates by scanning buglists. By putting the domain (only) in the
beginning of the summary it allows us to a) see the domain the issue is filed
against, and sort by the summary and get all bugs from a particular domain
together. See http://mozilla-evangelism.bclary.com/ for some other guidelines we
are using.
bank
Assignee: bclary → aruner
Component: US General → US Banks
QA Contact: zach → bclary
nominating mozilla0.9.9.

I'd also like to note that this isn't just a random banking site. The IBM
federal credit union (over 1 million members) uses this site for online banking
(among several other credit unions).
Keywords: mozilla0.9.9
http://www.premiermembers.org/javascript/swaptext.js does not detect Gecko.
Clearing keywords: 4xp, mozilla0.9.5, mozilla0.9.9, priority -> P1
taking
Assignee: aruner → bclary
Priority: -- → P1
Whiteboard: [USERAGENT]
Attached file navbar.html
The original swaptext.js script only had codeforks for Navigator 4 and Internet
Explorer. The attached version of swaptext includes a DOM code fork and works in
Gecko.

To see the working versions, view the navbar attachment.

contacted via web form. follow up in Feb.
Status: NEW → ASSIGNED
Target Milestone: --- → Feb
Arun, they claim security issues. I responded and cc'd nsdev-feedback.
security issues? I use this site (modulo the js menu) to do my banking
*everyday* with Netscape 6.x. AFAICT, the site is fully functional (modulo the
js menu)
http://www.premiermembers.org/javascript/hiermenus.js
Blocks: 85104
Severity: critical → major
OS: Windows 98 → All
Priority: P1 → P3
Hardware: PC → All
Summary: premiermembers.org - JS menu not working. → premiermembers.org - hiermenu 3 not working.
Whiteboard: [USERAGENT] → [USERAGENT] [hiermenu]
Whiteboard: [USERAGENT] [hiermenu] → [USERAGENT] [hiermenu][bank]
SPAM: New Components
Component: US Banks → English US
Target Milestone: Feb → ---
->default
Assignee: bc → english-us
Status: ASSIGNED → NEW
QA Contact: bc → english-us
one of the best references/recommendations I've found for encouraging financial institutions to support firefox is located at bankers on-line web site 

http://www.bankersonline.com/security/security_browserthreat070204.html 

It was written in 2004 during the download.ject attack, but much of it still applies today.  This is a good link to send when contacting banks.
Menus seem to work just fine now. I'm going to mark this FIXED; if there are outstanding issues with the site, please file new bugs.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
WORKSFORME is the appropriate resolution for bugs that work without a known fix.
Resolution: FIXED → WORKSFORME
(In reply to comment #16)
> WORKSFORME is the appropriate resolution for bugs that work without a known
> fix.

While this is generally true in the rest of Mozilla, it is generally *not* true in Tech Evangelism (or, at least, has not historically been the case).

Since this bug was confirmed by multiple trustworthy sources as being a TE bug, the only possible way it could have been resolved was for a fix to be applied on the other end, and since that was the whole point of having a TE bug in the first place, FIXED is entirely appropriate here.
Resolution: WORKSFORME → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: