i'm using gears to write a local application, and i need to be able to
get the full path of a file (such as an image) so i can insert it into
my rich text editor.  thanks to firefox's wonderful new security
policy, i can no longer use a simple <input type='file'> to retrieve
that value - all i get is the file name.  i then tried the openFiles
function in the desktop api of gears, but lo and behold - again, all i
get is the filename - no path!

1)  is gears just wrapping the browser's existing file input (in which
case, it's not gears limiting access to the file path)?
2)  if not, where in the source code for gears should i look to change
this restriction?

thanks,
imran

Reply via email to