Prev: opacity and MS (one more time)
Next: What's a good license for My Library?
From: Thomas 'PointedEars' Lahn on 5 Jan 2010 14:54
Scott Sauyet wrote:

> On Jan 5, 1:47 pm, "Paul Hovnanian P.E." <p...(a)hovnanian.com> wrote:
>> Scott Sauyet wrote:
>>> I've never tested to see whether "File > Save Page As" or its
>>> equivalents save some version of the dynamically altered page or the
>>> page as originally sent by the server. Even if the current crop of
>>> browsers all save the dynamic page (and I'd be surprised, honestly), I
>>> don't see that I could count on that behavior.
>>
>> From what I've seen, the original text copy is what is saved. Your JS
>> application modifies the objects that this was parsed into, but the text
>> copy is not modified. There could be a browser out there that does mod
>> the text, but I think that would be the exception.
>
> Actually, in my testing with FF, the altered page was stored, but when
> I reloaded it, the JS was run again, giving duplicate DOM
> manipulations...

That is why I said you should *rewrite* the document based on *its
serialization*.


PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$8300dec7(a)news.demon.co.uk>
First  |  Prev  | 
Pages: 1 2 3
Prev: opacity and MS (one more time)
Next: What's a good license for My Library?