Closed
Bug 1396707
Opened 7 years ago
Closed 4 years ago
failure to load animations/login on ClearStar.com
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: 1, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48
Build ID: 20170707010522
Steps to reproduce:
I was on seamonkey 3.* and upgraded to the current download 4.28.
I placed "clearstar.com" into navigation bar.
Actual results:
Main page loaded >>ALMOST<< normally.
4th line on screen search->archives should be animated/rotating.
under #1 since 1995 is a box the top 1/2 "security professionals" loaded normally
the bottom half "clearstar members only" is another animated feature
neither of these animations worked.
When I clicked on the "security professionals" box to login, I got a page saying "Authorization Required"
Expected results:
1. Search->Archives on line 4 should be animated.
2. the bottom half of the "security professionals" box saying "clearstar members only" should be animated, rather than blank
3. When the "security professionals" box is clicked, the "USERNAME/PASSWORD" box should pop-up in center of screen
This IS all working in firefox and chrome.
Comment 1•7 years ago
|
||
works fine with both official 2.48 and a local 2.49.1 build.
I suggest you chcck if you have put in some site permissions. Also try in safe mode and/or (prefered) a new test profile.
Reporter | ||
Comment 2•7 years ago
|
||
I'm more of a user than a techie - I only have one profile (that I know of) and have no idea how to do Site Permissions - or what kind of a permission I'd turn on or off - any ideas?
Comment 3•4 years ago
|
||
@Reporter:
You should ask for help at newsgroup mozilla.support.seamonkey on newsserver news.mozilla.org or subscribe SeaMonkey support mailing list with the same contents like newsgroup. You also can get Help on Reddit
Probably INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•