Why am I getting a yellow warning sign AND a blue border around my applet windows?
it started since update 10 I think
its a feature 
I think it is a replacement for the old “Java Applet Window” border on the botton of the window. Whats actually really anoying is, you can’t maximize the window anymore (even with signed applets…). There will be always the gap fo r the icon. I already filed a bug a few month ago which has been closed almost instantly after i filed it.
its a shit feature - now I have to explain world + dog why they have a yellow triangle attached on the right side of a window.
Damn it - why do applets and java have to be so broken to actually supply to customers 
[quote=“Matzon,post:3,topic:32623”]
[quote=“bienator,post:2,topic:32623”]
I don’t think Sun loves us anymore… :’(
It’s also annoying that the ‘contentpane border’ is BLINKING YELLOW the first second it gets focus! If you mess with lots of modal dialogs in your applet (well… at least I do), both the created dialog and upon closing, the ‘parent’ will BLINK!
[i]Dear customer,
My applet is dangerous, it has windows, which may confuse you.
It blinks all borders as a clear warning to you.
We’d prefer a fullscreen shroud, like Vista security popups, and play a sound.
As we like to say, a sad customer is better than a hacked customer.
Enjoy shopping!
[/i]
I think I’m going to window.alert() this message on the frontpage.
[quote]There will be always the gap fo r the icon. I already filed a bug a few month ago which has been closed almost instantly after i filed it.
[/quote]
Really? Have you tried it recently?
Dmitri
just tested with u11, same issue like in past with u10 ea. At least the “draggable applet restart from desktop” issue is fixed now in u11.
here is a testapp (i noticed it hits from time to time a deadlock… its only for debuging anyway):
https://fishfarm.dev.java.net/demo/
If you drag and maximize you you should see a gap on the right side of the screen.
(tested on win xp)
thats nothing - the early access versions kept it fleshing for around 5 seconds ;-).
This has got to stop.
Cas 
Ah, then it’s OK. :persecutioncomplex:
OK, I see. This will be fixed in 6u12 (to be released early next year). The flashing border goes away, and the warning icon will only be shown on “active” window.
Dmitri
WHY WHY WHY!!
Whats the point of punishing people that actually want to USE the platform.
What INSANE person thought it was a GOOD idea to add a f* warning icon on a window???
Do you know how many support requests we get because of an ODD looking Icon???
Sheesh, its like you want people to use flash instead.
I fully agree with Matzon. This security banner is pointless. There are many ways how to forge some system dialog asking for password/etc. Just some image based web can do that with imitation of common OS themes. IE can do fullscreen without problem, etc. Most of people uses default themes of few OS out there… So, please get rid of it. It just complicates our lives for correct usage.
Next issue is with unsigned/signed applets/webstart apps. You either can do very little, or you must have all privileges. Which is very wrong to ask the user, if the app just need for example: fullscreen mode, mic support, file access (at least the last is fixed with JRE 6u10 by allowing JNLP services in applets too). All these things can be done by asking user before first usage (and not before app runs) without exposing bigger risks such as full filesystem access.
[quote]IE can do fullscreen without problem, etc
[/quote]
nope, you can only with very old version maybe (5.5 and earlier), you cant with 6.0+, user have to press F11 for real fullscreen, website cannot force it.
[quote]Most of people uses default themes of few OS out there… So, please get rid of it. It just complicates our lives for correct usage.
[/quote]
the way it go is more that browser security are higher every day (less freedom ofcourse)
[quote]Next issue is with unsigned/signed applets/webstart apps. You either can do very little, or you must have all privileges. Which is very wrong to ask the user, if the app just need for example: fullscreen mode, mic support,
[/quote]
using micro or fullscreen in flash warn the visitor too and that’s a good thing no ?, flash just better know how to make those things look smoother and more natural.
Sorry didn’t recheck that lately, thanks for information.
Yes, but notice the important details, that a) users get informed what function app needs, b) app get access to just that function and not whole system… compare to Java where there is scary security dialog with certificate. I don’t have anything against that dialog, it’s very ok when you need some special stuff for example… but not for common tasks. It’s just not right to see too many applets that requires full privileges just for some common thing.
If you initiate a ‘Click & drag’ when the browser window is being displayed on anything but the primary display device, it completely stops repainting your window.
You have to drag the window onto your primary screen for the repainting to start working again ;D
Also, when you first initiate the Click & drag op (click/drag but dont release), the window dragging appears to be broken. It’s hard to determine exactly what is interferring with the dragging.
I have to drag/release/redrag for the window to have full freedom of movement across the desktop.
Anyone else experiencing similar behaviour? (this is all with u11 in FF)
maybe fishfarm is not the best example for demonstrating applets (it does a lot in background) but i think both issues you found are valid.
interresting, i have a dual head setup too - never saw this behavior. I remember once it wasn’t possible to drag the applet out of the main screen at all but i am not sure it it was windows or linux.
you should see similar behavior with the javafx samples. Something happens behind the scenes if you release the mouse the first time difficult to say what.
Just by building this app i filed around 5 bugs regarding the draggable applet against u10 ea releases. I had the feeling that the draggable applet feature wasn’t tested internally at all. It looked for me like the draggable applet was initially never intended to go for production and stay a proof of concept… well the rest of the storry is marketing.
(technically: what is the best unit test for the out-of-proccess applet? -> make it draggable)
Getting back to the security warning thing.
So what would you like to see? What’s the scenario you’d like your users to go through?
For the following cases:
- unsigned applet (doesn’t go full screen, or even maximize window)
- signed applet which attempts to execute some privileged operation
We’re discussing changes that could be made (probably in jdk7 time frame) so now
would be a good time to speak up (but be reasonable)…
Ideally, I’d like to see no warning for unsigned applet unless it gets maximized.
The problem is, of course, that showing a window is already a privileged operation
in some sense. It didn’t make sense to disallow it for unsigned applets, so they put a
warning on it instead.
The only reason I heard of for having the warning banner is to avoid spoofing -
presenting a user with a false page and leading them into entering their info or
something.
It would seem that if someone managed to stick a malicious applet onto a
page you’ll have bigger things to worry about, so may be this should be reconsidered.
For signed apps, there should be a way to specify exactly which privileged operations it is
intended to perform, and perhaps ask the user to allow/deny particular operations.
It would probably need to be done before the applet is started instead of when the operation
is about to be performed.
Any other ideas/comments?
Dmitri
Here ( http://demo.dzzd.net/FPSSample9/ ) is an example of an applet that starts without any security dialog.
Then, when the user requests to use better mouse control (that requires the use of the Robot class), a security dialog pops up.
It is a definate improvement over having a security dialog at startup as it gives a chance for the applet to inform the user that a security dialog will pop up.
It would be nice if it could say somthing like :
“Would you like to let this applet access your mouse?” <== ie Robot class
"Reason : "
where = “To enable the easier to use first person shooter mouse control.”
This example might look a bit ugly but to be honest its already ugly in the sense that it is scary.
In the short term, I’m told that there’s an internal API (in com.sun…) which allows the developer to control where the warning icon is placed (within window bounds, and it’s guaranteed to be visible).
So you could place it in the title bar, for example, so it’s less prominent. Not much help for undecorated windows though.
Dmitri