![]() |
|
![]() |
||
![]() |
![]() |
|
[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date] Re: <spoiler> element
From: Oskar Welzl <lists@welzl.info>
Date: Wed, 07 Dec 2005 18:03:31 +0100 To: Devin Bayer <devin@freeshell.org> Cc: Jeremy Rand <jeremy@asofok.org>, www-html@w3.org Message-Id: <1133975011.11974.4.camel@erde.hormayrgasse> Shall we try one more "XLink in XHTML 2.0"? Count my vote. - But I'm afraid I'm too late. Again. :-( Am Mittwoch, den 07.12.2005, 08:41 -0800 schrieb Devin Bayer: > Oskar Welzl wrote: > > > > I have to say, though, that HTML always offered the very generic "show > > this content only when activated by the user"-element: > > <a href="http://www.w3.org/TR/REC-html40/struct/links.html#h-12.2 ">Click > > here only if you want to read which element it is.</a> > > > > This is as generic as can be - and as specific as we can allow, > > probably. It is not the sophisticated "show within the current > > page"-solution you want. It does not fully cover all use cases: > > Disturbing medical photos within a scientific text should probably be > > shown right within the paragraph that describes them, not on a separate > > page. But that would be <show-disturbing-medical-pictures>, not just > > <spoiler> ;-) > > So, basically, the <spoiler> element is already provided with the XLink > language and the show="embed" attribute. This is esentialy the equivalent > of <a target="inline">. See: > > http://www.w3.org/TR/2001/REC-xlink-20010627/#show-att > > This is much more generic then <spoiler>, which for the most useful > applications is incorrectly named. > > -- Devin Bayer >Received on Wednesday, 7 December 2005 17:06:54 GMT |
|
||||||||||||||||