Aryeh Gregor schrieb:
On Thu, Oct 15, 2009 at 3:49 AM, Nelson Menezes
<[email protected]> wrote:
As an aside, there is a reason why AJAX has become so popular over the
past few years: it solves the specific UI-reset issue that is inherent
in full-page refreshes.
I'm trying to think what a solution to this would look like. Maybe
something like:
<static id=foo>Some stuff that doesn't change on page load...</static>
Changeable page content
<static id=bar>Some more stuff that doesn't change...</static>
Interesting idea! Anyway it introduces some consistency problems to
solve, e.g.:
Page1.html contains:
<static id="foo">I eat meat</static>
and links to page2.html, which contains:
<static id="foo">I am a vegetarian</static>
So page2.html looks different whether it is called from the link in
page1.html, or directly via a bookmark, external link, or manual URI input.
This could be solved if "static" elements have no content on their own,
but retrieve it from an external source. The identifyer is then not the
id attribute, but the source. This could be done with a src attribute on
the <static> element. But I assume an easier implementation would be
adding a "static" attribute for the <iframe> element, indicating that
the iframe contents should not be reloaded.
--
Markus
