[whatwg] At Inclusion (a declarative way to "Ajaxise" a website)

[Ian Hickson]

On Sun, 17 Jun 2012, Florent FAYOLLE wrote:
> 
> I have written a proposal that introduces a new way to include remote 
> contents into the document [...]

On Sun, 17 Jun 2012, Peter Beverloo wrote:
> 
> Without having read your proposal in detail, it seems like seamless 
> iframes in combination with <a target> should address the majority of 
> your use-case: 
> http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#attr-iframe-seamless

On Mon, 18 Jun 2012, Florent FAYOLLE wrote:
>
> That seems to cover a part of the use-case, indeed. However, using 
> Javascript instead of a declarative way to update the URL, I think, have 
> a major drawback: ensuring the indexation is not trivial.

Having a way to specify in the URL what to put into <iframe>s would indeed 
be an interesting idea. XFrames was a massively overengineered attempt at 
solving that solution, but maybe aspects of that idea could be resurrected?

Is there any browser vendor interest in addressing this?

(BTW, it may be worth reminding people of this FAQ entry that discusses 
how to propose new ideas:

http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F

In particular, a more careful examination of use cases and input from 
browser vendors is really important to a proposal's chances of success.)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'