- From: Russell O'Connor <roconnor@Math.Berkeley.EDU>
- Date: Fri, 25 Jan 2002 11:43:05 -0800 (PST)
- To: W3C HTML <www-html@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 25 Jan 2002, Masayasu Ishikawa wrote: > > Of course the correct answer is to require uppercase for all fragment > > identifiers. > > Since (at least some of major) existing user agents at the time HTML 4.0 > was developed recognized fragment identifiers case-sensitively, that > option was unrealistic, unfortunately. The discussion made it sound like this confusion was a result of differences in user agents. The problem seems to be with the HTML specification (er, recommendation) itself. The DTD and delcartaion imply that IDs are case insensitive, and name attributes are case sensitive. ... What is a poor user agent supposed to do? Since IDs weren't added until HTML 4.0, it seems reasonable for a user agent to match fragements case-senstively before HTML 4.0. (Unless there is something in HTML 3.2 that says otherwise). The above is wrt HTML 4.0. Presumably XHTML is entirely case sensitive since the complete move to unicode. - -- Russell O'Connor roconnor@math.berkeley.edu <http://www.math.berkeley.edu/~roconnor/> ``This is not a time, as it is never a time, to seek vengeance, but a time to seek the courage to forgive'' -- George W. Bush -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE8UbVOuZUa0PWVyWQRAuZvAKCZXbfuSSEwJ3umOl8mevSoN3gCVwCfRwDT XF9hlLagOT7LpDKbkUzia2k= =BamB -----END PGP SIGNATURE-----
Received on Friday, 25 January 2002 14:43:13 UTC