-
Notifications
You must be signed in to change notification settings - Fork 741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] 8.4: Document all new DOM classes and methods #4212
base: master
Are you sure you want to change the base?
Conversation
b40772e
to
6b116fb
Compare
5b1b19a
to
f762c1a
Compare
@Girgias I've finished with some basics. Most notably the class synopses are generated and the properties etc are all filled in. I've used xinclude quite a bit. I also fixed up some of the old DOM class descriptions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't test locally but this a pass across the whole PR
<row xml:id="constant.domstring-size-err"> | ||
<entry> | ||
<constant>DOMSTRING_SIZE_ERR</constant> | ||
<constant>DOMSTRING_SIZE_ERR</constant> / <constant>Dom\STRING_SIZE_ERR</constant> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue I can see for this, is that automatic linking for <constant>Dom\STRING_SIZE_ERR</constant>
is not going to work because the row has no corresponding XML ID.
Can an XML element have 2 IDs? If yes that would fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can an XML element have 2 IDs? If yes that would fix it.
No, but I don't think this is ever linked to directly 🤔
Thanks for the initial review. I pushed fixup commits so they can be validated individually, I'll later rebase this to merge the fixups with the original commits. |
@@ -7,7 +7,7 @@ | |||
<partintro> | |||
<section xml:id="dom-entity.intro"> | |||
&reftitle.intro; | |||
<xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) xpointer(id('domentity.intro')/db:simpara)"> | |||
<xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) xpointer(id('domentity.intro')/db:para)"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just Xinclude the whole introduction section instead of just including the para
? (same for some of the other pages)
<para> | ||
<simplelist> | ||
<member><link xlink:href="&url.spec.dom.living.comment;">WHATWG specification of Comment</link></member> | ||
</simplelist> | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for the wrapping para tag here (haven't checked all of the files, but it might be in others?)
<para> | ||
The <classname>Dom\Text</classname> class inherits from | ||
<classname>Dom\CharacterData</classname> and represents a text node. | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New file, so <simpara>
According to the DOM standard this requires a DTD which defines the | ||
attribute ID to be of type ID. You need to validate your document by | ||
passing <constant>LIBXML_DTDVALID</constant> to the parse method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personalization is used here.
<simpara> | ||
It is sometimes necessary to change | ||
the qualified name and namespace <acronym>URI</acronym> together in one | ||
step to not break any namespace rules. | ||
</simpara> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The splitting of the line here is a bit strange
<para> | ||
Adds nodes before the character data. | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simpara
<para> | ||
Removes the character data. | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simpara
<para> | ||
Replaces the character data with new nodes. | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simpara
<para> | ||
&return.void; | ||
</para> | ||
</refsect1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simpara
<para> | ||
<variablelist> | ||
<varlistentry> | ||
<term><parameter>selectors</parameter></term> | ||
<listitem> | ||
<simpara> | ||
A string containing one or more CSS selectors. | ||
</simpara> | ||
</listitem> | ||
</varlistentry> | ||
</variablelist> | ||
</para> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Para tag
Very WIP, not ready for review yet.
TODO:
Create examples of array indexing in NamedNodeMap ?Let's do this separately