From: Jeffrey Goldberg on
On 2010-03-16 4:21 PM, nospam wrote:

> html files are *text* files.

With executable bits of text thanks to the invention of JavaScript.

> if it's really
> so dangerous, why isn't safari warning people when the html is
> originally downloaded?

It would be nice if there were a good no-script plugin for Safari as
there is for Firefox.

-j


--
Jeffrey Goldberg http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
From: nospam on
In article <80ir3bFa92U1(a)mid.individual.net>, Jeffrey Goldberg
<nobody(a)goldmark.org> wrote:

> > html files are *text* files.
>
> With executable bits of text thanks to the invention of JavaScript.

but they don't execute in a text editor such as text wrangler, yet that
warning still appears when opening them.
From: dorayme on
In article <190320101950296373%nospam(a)nospam.invalid>,
nospam <nospam(a)nospam.invalid> wrote:

> In article <80ir3bFa92U1(a)mid.individual.net>, Jeffrey Goldberg
> <nobody(a)goldmark.org> wrote:
>
> > > html files are *text* files.
> >
> > With executable bits of text thanks to the invention of JavaScript.
>
> but they don't execute in a text editor such as text wrangler, yet that
> warning still appears when opening them.

At the point at which the warning occurs, does the OS know what
it is being attempted to open it in? Suppose not. It opens in
BBedit or TW, you drag the file name from the drawer ontoa
browser and ... will the OS or browser know where it has come
from? When someone or something decides to do some nannying,
there is no limit to the interference!

--
dorayme
From: Jeffrey Goldberg on
On 2010-03-19 9:50 PM, nospam wrote:
> In article <80ir3bFa92U1(a)mid.individual.net>, Jeffrey Goldberg
> <nobody(a)goldmark.org> wrote:
>
>>> html files are *text* files.
>>
>> With executable bits of text thanks to the invention of JavaScript.
>
> but they don't execute in a text editor such as text wrangler, yet that
> warning still appears when opening them.

The OS has no way to know whether what you are opening it with will run
the JavaScript or not.

Note that if Adobe has their way, we will soon have the same problem
with PDFs.

-j


--
Jeffrey Goldberg http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
From: nospam on
In article <80k74uFac7U1(a)mid.individual.net>, Jeffrey Goldberg
<nobody(a)goldmark.org> wrote:

> The OS has no way to know whether what you are opening it with will run
> the JavaScript or not.

obviously, it needs to. the way it works now is *broken*.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: FREE MAC!
Next: iTunes 9 and iPod hard drives