I have a patch in my tree that moves lowercasing of tag/attribute names back into the tokenizer class rather than being part of the normalizeToken method in the parser class. The case foling is controlled by an attribute so the XML parser is able to switch of case folding. There are several reasons this approach may be preferable to what we currently have (following an IRC discussion with Phillip Tayloy and hsivonen):
Easier to share tokenizer test cases with other projects Elimination of duplicate attributes follows the text of the spec more closely Future additions to HTML may include case-sensitive names e.g. if <svg> subtrees are ever introduced Are there any strong objections to checking in this change? It passes our existing tests. -- "Mixed up signals Bullet train People snuffed out in the brutal rain" --Conner Oberst --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to html5lib-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4