Re: Edit javascript in IE
"Dr John Stockton" <spam@merlyn.de mon.co.uk> wrote in message
news:VVfpplE4st b$EwPB@merlyn.d emon.co.uk...[color=blue]
> JRS: In article <3f6d4c72$0$348 95$1b62eedf@new s.wanadoo.nl>, seen in
> news:comp.lang. javascript, Ivo <no@thank.you > posted at Sun, 21 Sep 2003
> 09:02:27 :-[color=green]
> >Follows a bookmarklet that will a page's generated source (that is: the
> >source including script tags and anything the script may have contibuted[/color][/color]
to[color=blue][color=green]
> >the page) in a new window which has
> >1. a textarea where you can edit the code
> >2. an button "Apply" that overwrites the page with your edited version.
> >3. a "Restore" button that will attempt to, eh, restore the old page.[/color]
>
> ISTM that the technique, while convenient and ingenious, may be
> vulnerable to loss.
> (...)
> My browser instance was locked, for example, by the posted code of the
> "decompress or", perhaps because I'd failed to spot a line-wrap. Other
> instances kept running, but all died when I tried to kill the locked
> one.
> © John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 IE[/color]
4 ©
Absolutely. Sometimes I want to backup a testpage but not create a whole new
file for it. Remembering to remove that later on is just too much work.
The clipboard is then a most convenient place to temporariliy store the
original code. Not the safest place, and when the test is powerful enough to
crash the computer, things get lost, yes.
Methinks that the weak points of the ideas that have been put forward, are
clear enough, but that the original request aimed for something as simple as
poss, with no intent to save the edited file or opening of other programs.
Sorry, which decompressor code?
Ivo
"Dr John Stockton" <spam@merlyn.de mon.co.uk> wrote in message
news:VVfpplE4st b$EwPB@merlyn.d emon.co.uk...[color=blue]
> JRS: In article <3f6d4c72$0$348 95$1b62eedf@new s.wanadoo.nl>, seen in
> news:comp.lang. javascript, Ivo <no@thank.you > posted at Sun, 21 Sep 2003
> 09:02:27 :-[color=green]
> >Follows a bookmarklet that will a page's generated source (that is: the
> >source including script tags and anything the script may have contibuted[/color][/color]
to[color=blue][color=green]
> >the page) in a new window which has
> >1. a textarea where you can edit the code
> >2. an button "Apply" that overwrites the page with your edited version.
> >3. a "Restore" button that will attempt to, eh, restore the old page.[/color]
>
> ISTM that the technique, while convenient and ingenious, may be
> vulnerable to loss.
> (...)
> My browser instance was locked, for example, by the posted code of the
> "decompress or", perhaps because I'd failed to spot a line-wrap. Other
> instances kept running, but all died when I tried to kill the locked
> one.
> © John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 IE[/color]
4 ©
Absolutely. Sometimes I want to backup a testpage but not create a whole new
file for it. Remembering to remove that later on is just too much work.
The clipboard is then a most convenient place to temporariliy store the
original code. Not the safest place, and when the test is powerful enough to
crash the computer, things get lost, yes.
Methinks that the weak points of the ideas that have been put forward, are
clear enough, but that the original request aimed for something as simple as
poss, with no intent to save the edited file or opening of other programs.
Sorry, which decompressor code?
Ivo
Comment