- From: Rob Manson <roBman@mob-labs.com>
- Date: Sun, 07 Aug 2011 13:47:24 +1000
- To: "public-poiwg@w3.org" <public-poiwg@w3.org>
Hi Karl, if we aim to make this standard work within html5 then you're absolutely right. However, if it's targeting other types of browsers and other contexts then I think there is some merit in being able to serialise the payload of a link (the bit between the >*< ) while still identifying it's canonical source (href=canonical_source). It is definitely a logical possibility. And if the standard supported this but did not require it then html5 compatibility could still be maintained too (maybe as a profile). roBman On Sat, 2011-08-06 at 20:26 -0400, Karl Dubost wrote: > Hi, > > FYI > This following one will not work. > > > external link with inline content > > > > <link rel="thing" href="url_to_canonical_source_for_thing_stuff"> > > serialised inline thing stuff goes here > > </link> > > The browser will auto-correct the link by closing it and putting the text outside. Not what you expect. > http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1096 > >
Received on Sunday, 7 August 2011 03:47:52 UTC