on 1/21/08 10:31 AM, chrismarx at [EMAIL PROTECTED] wrote:

> 
> i believe this is expected behavior, it would be a security risk to
> allow script access to file inputs-
> 
> On Jan 20, 7:32 pm, "Steffan A. Cline" <[EMAIL PROTECTED]> wrote:
>> on 1/6/08 11:55 PM, chrismarx at [EMAIL PROTECTED] wrote:
>> 
>> 
>> 
>> 
>> 
>>> best to see the live page-
>> 
>>> On Jan 6, 9:32 pm, "Steffan A. Cline" <[EMAIL PROTECTED]> wrote:
>>>> on 1/6/08 5:29 PM, chrismarx at [EMAIL PROTECTED] wrote:
>> 
>>>>> first, it would be better jquery technique to bind your img outside of
>>>>> the onclick
>> 
>>>>> $('#imgID').click(function(){
>>>>>          $('#logo').click();
>>>>> });
>> 
>>>>> what function is executed when you trigger the click event on the logo
>>>>> input?
>> 
>>>>> On Jan 6, 5:46 pm, "Steffan A. Cline" <[EMAIL PROTECTED]> wrote:
>>>>>> Running into something strange. I have an image with an onclick handler
>>>>>> that
>>>>>> calls on a hidden <input type="file" id="logo" ....> via
>>>>>> <img src="xx" onclick="$('#logo').click()">
>>>>>> This works flawlessly in Safari, IE 6 & 7 but not in FF Mac (not sure
>>>>>> about
>>>>>> PC). Any ideas?
>> 
>>>>>> Also, what is the best way when taking this approach? I have it where the
>>>>>> file input is in a div. I initially tried using display:none for the
>>>>>> container div but the file inputs stopped working. I changed the div to
>>>>>> visibility:hidden and height: 0px and it works (with the exception above)
>>>>>> anyone have a better suggestion on how to hide these inputs better?
>> 
>>>>>> I am using jquery 1.1.3.1
>> 
>>>>>> Suggestions?
>> 
>>>>>> Thanks
>> 
>>>>>> Steffan
>> 
>>>> I am hiding the file inputs and then parsing the data from the file input
>>>> onchange and placing it into a dummy text field so that there are no paths
>>>> etc when the end user views it. As you know, some browsers prepend the path
>>>> to the name in the file input and I wasn't thrilled with that. By trimming
>>>> the path and displaying only the file name looked more appealing. The end
>>>> user wants to have their own add/delete buttons for the images rather than
>>>> the standard "choose" button. The odd thing is that when I use the DOM
>>>> inspector in FF it shows that the image has the click attribute so I am not
>>>> sure why it's not firing. Would it beneficial to show all of the code or is
>>>> there enough mentioned to see why the click event fails? Odd that FF does
>>>> not show any errors or warnings in the error console.
>> 
>>>> Thanks
>> 
>>>> Steffan
>> 
>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
>> 
>> <html xmlns="http://www.w3.org/1999/xhtml";>
>> <head>
>>     <title></title>
>>     <script type="text/javascript"
>> src="/js/jquery-1.1.3.1.pack.js"></script>
>> </head>
>> 
>> <body>
>>     <input type="button" onclick="$('#inFile').click()" value="Find It">
>>     <div style="">
>>         <input type="file" name="test" id="inFile">
>>     </div>
>> </body>
>> 
>> </html>
>> 
>> As stated it works in Safari and IE6&7. Any ideas why it fails in Firefox?
>> 
>> Thanks
>> 
>> Steffan
>> 
I fail to see how the .click() could be a security issue that Safari and
IE6&7 missed out on. Is possible that there is a flaw in this version of FF
or jQuery?


Thanks

Steffan

---------------------------------------------------------------
T E L  6 0 2 . 7 9 3 . 0 0 1 4 | F A X  6 0 2 . 9 7 1 . 1 6 9 4
Steffan A. Cline 
[EMAIL PROTECTED]                             Phoenix, Az
http://www.ExecuChoice.net                                  USA
AIM : SteffanC          ICQ : 57234309
YAHOO : Steffan_Cline   MSN : [EMAIL PROTECTED]
GOOGLE: Steffan.Cline             Lasso Partner Alliance Member
---------------------------------------------------------------



Reply via email to