- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Feb 2011 10:07:41 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12106
Summary: 1. <quote> <!DOCTYPE HTML> </quote> Is this
declaration part of an html document? Or is this part
of a Document Type Definition (DTD)? Where are DTDs
for html documents defined? 2. <title> Resource
metadata management </title> <quote> A Document is
always
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#top
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#top
Comment:
1.
<quote>
<!DOCTYPE HTML>
</quote>
Is this declaration part of an html document? Or is this part of a Document
Type Definition (DTD)? Where are DTDs for html documents defined?
2.
<title>
Resource metadata management
</title>
<quote>
A Document is always set to one of three modes: no-quirks mode, the default;
quirks mode, used typically for legacy documents; and limited-quirks mode,
also known as "almost standards" mode. The mode is only ever changed from the
default by the HTML parser, based on the presence, absence, or value of the
DOCTYPE string.
</quote>
Where do I define, which of the above modes a document is in?
3.
<title>
Common infrastructure
Terminology
</title>
<quote>
This specification refers to both HTML and XML attributes and IDL attributes,
</quote>
Does this specification refers to all three or only to two (both?) of the
above attribute series?
In the entire document it remains unclear, whether the standard pertains only
to static html/xhtml (as e.g. sent from a web server) or also to dynamic
html/xhtml (as e.g. produced by javascript invoked by user interaction). User
Agents, in some cases, behave differently when receiving a text/html document
from the web server, as opposed to when they execute javascript commands to
generate dynamically the same content.
Are such User Agents not-conforming to this standard?
4.
<title>
The meta element
</title>
<quote>
The charset attribute specifies the character encoding used by the document.
This is a character encoding declaration. If the attribute is present in an
XML document, its value must be an ASCII case-insensitive match for the string
"UTF-8" (and the document is therefore forced to use UTF-8 as its encoding).
Note: The charset attribute on the meta element has no effect in XML
documents, and is only allowed in order to facilitate migration to and from
XHTML.
</quote>
Could you please make a statement, that the character encoding of an XML
attribute is defined by the Document Type Definition (e.g. <?xml version="1.0"
encoding="utf-8"?>
5.
Regarding the examples:
I would expect, that in a standard document the examples are reproducible in
all aspects, so that when I try an example in a User Agent, I get exactly what
the document says, the example should produce. This is, however, not the case
in many examples for
<title>
Tabular Data
</title>
At least as far as border reproduction is concerned, practically all examples
fail, i.e. the examples do not show the border as it should according to the
document. And an example, which makes me first search the error does not help
very much.
Thank you very much for your attention.
suomi@ayni.com
Posted from: 212.90.206.130
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 17 February 2011 10:07:43 UTC