admin
doz
html2pdf_v4.03
htmlpurifier-4.10.0
art
benchmarks
configdoc
docs
dtd
entities
examples
specimens
dev-advanced-api.html
dev-code-quality.txt
dev-config-bcbreaks.txt
dev-config-naming.txt
dev-config-schema.html
dev-flush.html
dev-includes.txt
dev-naming.html
dev-optimization.html
dev-progress.html
enduser-customize.html
enduser-id.html
enduser-overview.txt
enduser-security.txt
enduser-slow.html
enduser-tidy.html
enduser-uri-filter.html
enduser-utf8.html
enduser-youtube.html
fixquotes.htc
index.html
proposal-colors.html
proposal-config.txt
proposal-css-extraction.txt
proposal-errors.txt
proposal-filter-levels.txt
proposal-language.txt
proposal-new-directives.txt
proposal-plists.txt
ref-content-models.txt
ref-css-length.txt
ref-devnetwork.html
ref-html-modularization.txt
ref-proprietary-tags.txt
ref-whatwg.txt
style.css
extras
library
maintenance
plugins
smoketests
tests
.gitattributes
.gitignore
.travis.yml
CREDITS
Doxyfile
INSTALL
INSTALL.fr.utf8
LICENSE
NEWS
README.md
TODO
VERSION
WHATSNEW
WYSIWYG
composer.json
phpdoc.ini
images
prints
prints3
proseminar
Kennwortwechsel.php
hauptframe.php
index.php
index_alt.php
index_db.php
index_frame.htm
index_ldap.php
login.php
logout.php
menuframe.htm
styles_pc.css
topframe.php
27 lines
1.1 KiB
Plaintext
Executable File
27 lines
1.1 KiB
Plaintext
Executable File
|
|
Web Hypertext Application Technology Working Group
|
|
WHATWG
|
|
|
|
== HTML 5 ==
|
|
|
|
URL: http://www.whatwg.org/specs/web-apps/current-work/
|
|
|
|
HTML 5 defines a kaboodle of new elements and attributes, as well as
|
|
some well-defined, "quirks mode" HTML parsing. Although WHATWG professes
|
|
to be targeted towards web applications, many of their semantic additions
|
|
would be quite useful in regular documents. Eventually, HTML
|
|
Purifier will need to audit their lists and figure out what changes need
|
|
to be made. This process is complicated by the fact that the WHATWG
|
|
doesn't buy into W3C's modularization of XHTML 1.1: we may need
|
|
to remodularize HTML 5 (probably done by section name). No sense in
|
|
committing ourselves till the spec stabilizes, though.
|
|
|
|
More immediately speaking though, however, is the well-defined parsing
|
|
behavior that HTML 5 adds. While I have little interest in writing
|
|
another DirectLex parser, other parsers like ph5p
|
|
<http://jero.net/lab/ph5p/> can be adapted to DOMLex to support much more
|
|
flexible HTML parsing (a cool feature I've seen is how they resolve
|
|
<b>bold<i>both</b>italic</i>).
|
|
|
|
vim: et sw=4 sts=4
|