Re: Deleting effect like icon-recycle bin



Luke Matuszewski wrote:

> Thomas 'PointedEars' Lahn napisal(a):
>> > <img id="to_remove" title="File unnecessary" />
>> ^
>> IE does not support XHTML, --------------------'
>> and in HTML that is equivalent to "<img ...>&gt;",
>> unless falsely error-corrected.
>
> This statement is wrong in my assumption.

Your assumption is what is wrong here.

> For HTML source code the appropriate parser is called 'soap parser'.

The appropriate parser für HTML is an SGML parser as that is an SGML
application per its Specifications.[1] That few Web browsers use such
a strict parser does not make the parsed code correct or even Valid,
because Web browsers are only a subset of HTML user agents. Therefore
I wrote "falsely error-corrected"; that false error-correction (correct
would be to render the markup as described) is part of the behavior of
"_tag soup_ parsers" in Web browsers; it is not of the W3C Markup
Validator[2], _e.g._

Non-Valid markup is non-interoperable markup, which is a Bad Thing.[3]

> It means that is it will skip all not known elements of markup'.

The SGML SHORTTAG feature that is enabled for HTML is not an unknown
element of HTML markup. It is well specified[4] and documented, and
even partially supported by current implementations.[5]

> is perfectly good - it is well 'understood' by common HTML parsers

If they do not understand it as "<img ...>&gt;", those are _not_ really
HTML parsers, but, as you tried to point out, "tag soup parsers".

> and furthermore it is valid under XHTML.

As one of the major browsers (IE) still does not support XHTML, that
does not bear any meaning regarding the usefulness of that code. Take

<script type="text/javascript" src="foo.js" />

for example, which is perfectly Valid XHTML but will probably not work as
supposed in IE even if declared as such: first thing is that IE does not
support the proper media type for XHTML, application/xhtml+xml; second is
that if that markup is served with the media type text/html, the above is
probably parsed (due to the mentioned false error-correction) to the HTML
markup

<script type="text/javascript" src="foo.js">

The `script' element would be not closed, hence all following markup was
considered script code which would probably cause this content not to be
displayed and instead cause a SyntaxError in that UA.[6]

Those are well-known facts that have often (enough) been discussed here.[7]

See also <URL:http://hixie.ch/advocacy/xhtml>


PointedEars
___________
[1] <URL:http://www.w3.org/TR/REC-html32>
<URL:http://www.w3.org/TR/html4/>
<URL:https://www.cs.tcd.ie/15445/15445.html>
<URL:http://rfc-editor.org/rfc/rfc2854.txt>
[2] <URL:http://validator.w3.org/>
[3] <URL:http://diveintomark.org/archives/2003/05/05/why_we_wont_help_you>
[4] <URL:http://www.w3.org/TR/html4/sgml/sgmldecl.html>
[5] <URL:http://www.dodabo.de/html+css/tests/shorttag.html>
[6]
<URL:http://groups.google.com/group/comp.lang.javascript/msg/ecfcb617605ae5d1?as_umsgid=1323309.yscONmSHSj@xxxxxxxxxxxxxx>
[7]
<URL:http://groups.google.com/groups?as_q=XHTML&as_ugroup=comp.lang.javascript&scoring=d&filter=0>
.



Relevant Pages

  • Re: Javascript and IE? Javascript and C#?
    ... DOM scripts operate on specific markup. ... It is deprecated in HTML 4.01 _for the `applet' element_ only, ... It is not even deprecated for `a' elements in XHTML 1.0: ... Utter nonsense, see above. ...
    (comp.lang.javascript)
  • Re: Javascript newbie - Please Help
    ... but would use XHTML anyway out of the same lack of knowledge, ... using them could easily render their markup invalid. ... consequences in a UA with a more strict parser. ...
    (comp.lang.javascript)
  • Re: Markup Validation Service ??
    ... You're using XHTML 1.0 Transitional Appendix C ... Transitional markup is usually a bad idea for a new site. ... I suggest you use HTML 4.01 Strict instead of any XHTML. ... generating a valid site. ...
    (comp.infosystems.www.authoring.html)
  • Re: Javascript and Vista
    ... XHTML 1.0 Appendix C, the two markup languages are inherently incompatible. ... True - and this would most certainly prevent HTML being served as ...
    (comp.lang.javascript)
  • Re: Any suggestions about (quotes or )
    ... XHTML has no impact on HTML, though it is good practice to quote all attributes and include optional tags. ... The errors in the posted markup means it doesn't conform to any markup language, let alone hint at the strict requirements of XHTML. ...
    (comp.lang.php)

Loading