Closed Bug 136590 Opened 23 years ago Closed 22 years ago

java security dialog beachballs the client

Categories

(Core Graveyard :: Java: OJI, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: tvl, Assigned: bnesse)

References

()

Details

http://www.guardiancam.com uses a java applet for it's video feeds, they changed the site over this past weekend, and I now get a security dialog about the applet being signed. this beachballs the os x mac client; you can't seem to click on the dialog to get the applet run. i should also point out, that before this rev of the applet, it used to be that mozilla crashed every time the window was closed. this is with the 1.0b2 MRJ plugin.
should probably go to someone at nscp --> bnesse. cc'ing dagley and beard.
Assignee: joe.chou → bnesse
Status: UNCONFIRMED → NEW
Ever confirmed: true
It appears that you need to be a member in order to actually see this. I can't find a link to a demo cam...
then we need to work with them to get a test account.
Thomas, any chance this was fixed with fc1? :)
the security dialog has gone away (i think they tweaked the applet). i still get a crash on closing the java window. should i file another bug on that? do the nightlies have symbols, i can attach a crash log? (or do you want a log off of rc1 w/ fc1?)
No need to file a new bug. We can continue to use this one. Yes please attach a crash log. The nightlies do have symbols. I generally have a more current trunk build than a branch build, so a nightly would be preferential, but rc1/fc1 is fine too. What ever you have handy.
i can't get the nightly to fail, so maybe it's been fixed? i'll try to pull a nightly again in a few days and check again to make sure it still doesn't crash.
Marking wfm (using the demo page). Tested under 2002-10-14-03 trunk with 10.2.1
Status: NEW → RESOLVED
Closed: 22 years ago
QA Contact: pmac → petersen
Resolution: --- → WORKSFORME
verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.