[Flashcoders] browser security aggrevations (rant alert)

2007-04-24 Thread Andreas R
basic banner. you click on something, a url opens. However, this process 
has to go through a delegate. User clicks, releases; bam,

Adobe flash player has stopped a potentially unsafe operation

Banner has a search bar, enter key, when this inputfield has focus, 
calls getURL. Nuh uh.

Adobe flash player has stopped a potentially unsafe operation

anything using externalinterface
Adobe flash player has stopped a potentially unsafe operation

getURL calls through event bubbling or event chains
Adobe flash player has stopped a potentially unsafe operation

getURL calls through onPress (bear with me)
Adobe flash player has stopped a potentially unsafe operation

The amount of shit we have to go through to make stuff work in browsers 
is one thing (such as raping our own script to the point of hilarity), 
but why, oh dear sweet baby jesus why, is Adobe forcing endusers to use 
their ridiculous fucking security manager page?!


I have rarely seen a more user unfriendly piece of garbage. Nothing is 
clear, descriptions are vague, and somehow the whole tone seems directed 
at.. developers?


Either i'm doing something fundamentally wrong, and by fundamentally i'm 
talking triangular wheels type shit, or someone needs to explain to me 
the thought process behind putting users through such a meat grinder of 
a security control panel, because the way i see it right now, we're up 
shit creek if we want to deliver content with a semblance of proper 
usability and avoid users getting smushed into that security alert again 
and again.


My mom would have *no idea whatsoever* why that thing showed up, nor 
what the security manager site even does.


To remain objective:
Here's my problem. X number of buttons in a class where button presses 
broadcast click events that do a number of things, including opening a url.
Also, the search bar problem described above. In an ideal world all 
these cals would go through javascript with externalinterface (it's a 
somewhat complex banner and i'd like the client to be able to alter 
where URLs point for instance), but that's a surefire way of forcing 
endusers to go through the grinder if they haven't already, degrading 
the whole application to the power of max.


I have a hell of a time figuring out how to do this, and it's beginning 
to royally anger me.


So please, smarter people than i; How do you facilitate user 
interactions with the browser without crashing into this lunatic 
security management solution? What are the rules of thumb?


*sigh*

- Andreas R
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


Re: [Flashcoders] browser security aggrevations (rant alert)

2007-04-24 Thread Иван Дембицкий

Andreas,

try test your movies in internet.

--
iv
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


RE: [Flashcoders] browser security aggrevations (rant alert)

2007-04-24 Thread Holth, Daniel C.

Andreas,

Are you testing on a webserver or locally?  I rarely get errors from
using ExternalInterface or getURL calls when testing online... 

Flash security is horrible to work with locally (hard-drive, CD-ROM,
etc) and it can be a real nuisance to have to always upload your files
to the webserver in order to test, but once online it goes pretty
smooth.
  
Daniel Holth
I.S. Programmer


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andreas
R
Sent: Tuesday, April 24, 2007 11:14 AM
To: flashcoders@chattyfig.figleaf.com
Subject: [Flashcoders] browser security aggrevations (rant alert)

basic banner. you click on something, a url opens. However, this process

has to go through a delegate. User clicks, releases; bam,
Adobe flash player has stopped a potentially unsafe operation

Banner has a search bar, enter key, when this inputfield has focus,
calls getURL. Nuh uh.
Adobe flash player has stopped a potentially unsafe operation

anything using externalinterface
Adobe flash player has stopped a potentially unsafe operation

getURL calls through event bubbling or event chains
Adobe flash player has stopped a potentially unsafe operation

getURL calls through onPress (bear with me)
Adobe flash player has stopped a potentially unsafe operation

The amount of shit we have to go through to make stuff work in browsers
is one thing (such as raping our own script to the point of hilarity),
but why, oh dear sweet baby jesus why, is Adobe forcing endusers to use
their ridiculous fucking security manager page?!

I have rarely seen a more user unfriendly piece of garbage. Nothing is
clear, descriptions are vague, and somehow the whole tone seems directed

at.. developers?

Either i'm doing something fundamentally wrong, and by fundamentally i'm

talking triangular wheels type shit, or someone needs to explain to me
the thought process behind putting users through such a meat grinder of
a security control panel, because the way i see it right now, we're up
shit creek if we want to deliver content with a semblance of proper
usability and avoid users getting smushed into that security alert again

and again.

My mom would have *no idea whatsoever* why that thing showed up, nor
what the security manager site even does.

To remain objective:
Here's my problem. X number of buttons in a class where button presses
broadcast click events that do a number of things, including opening a
url.
Also, the search bar problem described above. In an ideal world all
these cals would go through javascript with externalinterface (it's a
somewhat complex banner and i'd like the client to be able to alter
where URLs point for instance), but that's a surefire way of forcing
endusers to go through the grinder if they haven't already, degrading
the whole application to the power of max.

I have a hell of a time figuring out how to do this, and it's beginning
to royally anger me.

So please, smarter people than i; How do you facilitate user
interactions with the browser without crashing into this lunatic
security management solution? What are the rules of thumb?

*sigh*

- Andreas R
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

This e-mail and its attachments are intended only for the use of the 
addressee(s) and may contain privileged, confidential or proprietary 
information. If you are not the intended recipient, or the employee or agent 
responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution, displaying, copying, or 
use of this information is strictly prohibited. If you have received this 
communication in error, please inform the sender immediately and delete and 
destroy any record of this message. Thank you.
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


Re: [Flashcoders] browser security aggrevations (rant alert)

2007-04-24 Thread Muzak
 So please, smarter people than i; How do you facilitate user interactions 
 with the browser without crashing into this lunatic 
 security management solution? What are the rules of thumb?

You might want to start here:

http://www.adobe.com/resources/security/
http://www.adobe.com/ap/products/flashplayer/security/

http://www.adobe.com/devnet/flashplayer/articles/flash_player_8_security.pdf
http://www.adobe.com/devnet/flashplayer/articles/fp8_security-related_apis.pdf

regards,
Muzak


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com