Re: multi browser forms issue

From	David Mark <dmark.cinsoft@gmail.com>
Newsgroups	comp.lang.javascript
Subject	Re: multi browser forms issue
Date	2011-11-07 13:05 -0800
Organization	http://groups.google.com
Message-ID	<858f3485-5cf5-41f1-b4be-e8619d3ac867@k38g2000pro.googlegroups.com> (permalink)
References	<a9622d31-d06a-4886-8a6d-b90e8a1781ef@o19g2000vbk.googlegroups.com> <6b248eda-8b2d-4618-af26-d3983cdcdbb1@u10g2000prl.googlegroups.com> <m2y5vsnl21.fsf@nntp.bednarz.nl>

Show all headers | View raw

On Nov 7, 8:01 am, Eric Bednarz <bedn...@fahr-zur-hoelle.org> wrote:
> David Mark <dmark.cins...@gmail.com> writes:
> >> <!DOCTYPE HTML>
>
> > Why are you using HTML5?
>
> That’s not ‘using HTML5’, that’s choosing a rendering mode in a mnemonic
> fashion, and without the cargo cult parts that do nothing.

What else could it possibly mean, except this person intends to use
HTML5 markup (or is just copying and pasting patterns). Yes, I know
what the doctype does and I can't imagine why anybody would transplant
an HTML5 doctype onto a document that fits squarely into HTML4.

>
> > Many browsers in use (e.g. most versions of
> > IE) don't know what it is. And seeing as multi-browser consistency is
> > eluding you...
>
> Many (besides academical experiments, I'd say all) browsers don’t know
> what SGML is, still lots of websites try to look like (parts of) SGML
> documents.
>
> Having said that, the above document type declaration meets the SGML
> production for ‘document type declaration’. Go figure.

So what? It's still stupid to use that doctype at this time (unless
you actually intend to use HTML5 markup). I don't care is "all
browsers" avoid quirks mode with that one.

Of course, as most Web developers used to label their tag soup XHTML
transitional, this new trend could be considered an improvement.

>
> >> <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>
> > That's not right for HTML5.
>
> There seem to be quite some things eluding you, too…

Wrong. Once again, I am pointing out how silly it is to transplant an
HTML5 doctype onto a document that is clearly not HTML5.

Thread

multi browser forms issue Dizzee <slightlyandy@gmail.com> - 2011-11-06 14:07 -0800
  Re: multi browser forms issue Denis McMahon <denismfmcmahon@gmail.com> - 2011-11-06 22:38 +0000
  Re: multi browser forms issue David Mark <dmark.cinsoft@gmail.com> - 2011-11-07 04:40 -0800
    Re: multi browser forms issue Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-07 14:01 +0100
      Re: multi browser forms issue Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-07 14:13 +0100
        Re: multi browser forms issue Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-07 14:58 +0100
          Re: multi browser forms issue Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-07 15:51 +0100
      Re: multi browser forms issue "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2011-11-07 16:08 +0200
      Re: multi browser forms issue David Mark <dmark.cinsoft@gmail.com> - 2011-11-07 13:05 -0800
        Re: multi browser forms issue Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-07 23:07 +0100
          Re: multi browser forms issue Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-07 23:26 +0100
            Re: multi browser forms issue Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-09 20:17 +0100
              Re: multi browser forms issue Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-10 18:42 +0100
                Re: multi browser forms issue Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-11 23:38 +0100

csiph-web