Re: Re[2]: Printing from JS

["Brian Karlak" <bkarlak@panbio.com>]

On Mar 22,  2:39am, jnavarro@mcgraw-hill.com wrote:
> Subject: Re[2]: Printing from JS

> Printing may be bad from within JS, however, we will be rolling out an
> Intranet application in our company that will require some type of printing.
> I will bet that this may be an issue as more and more companies begin
> deploying Netscape and JS as a solution to client/server.

Come to think of it, though: if a hypothetical JS print command existed that
only brought up a Netscape "Print . . ." dialog box, would that be a security
risk?  The user would be aware that a print request was being made and could
accept it or cancel it at her discretion.

The same method could be used for client file read/writes as well . . . "Click
here to save this page to your disk" would bring up a file dialog.  User
control of file path, etc = no security risk, right?  (i think so, at least . .
.)

Brian

-- 
  d a t a b a s e s    a r e   i n   o u r  g e n e s
  ----------------------------------------------------
  Brian Karlak   bkarlak@panbio.com  (510) 337-7910 ph
  Manager, SciApps Group             (510) 522-9394 fx
  ----------------------------------------------------
  P  A  N  G  E  A     S  Y  S  T  E  M  S     I  N  C
--------------------------------------------------------------------
For help about the list, please send a message to 'majordomo@obscure.org'
with the message body 'help'. To unsubscribe, send a message to
'majordomo@obscure.org' with the message body 'unsubscribe javascript'.
List archives and pointer to FAQ: http://www.obscure.org/javascript/