This repository has been archived by the owner on Sep 14, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #39 from PolymerLabs/justin-work
Upgrade to parse5 2.2
- Loading branch information
Showing
5 changed files
with
75 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,4 @@ language: node_js | |
sudo: false | ||
node_js: | ||
- "6" | ||
- "5" | ||
- "4" | ||
- "0.12" | ||
- "0.10" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Change Log | ||
|
||
## [v2.0.0](https://github.com/PolymerLabs/dom5/tree/v2.0.0) (2016-09-23) | ||
- Upgraded to parse5 v2.2.1 | ||
- (*breaking*) Because parse5 2.x correctly handles `<template>` elements, | ||
the nodeWalk* and query* functions will no longer return results from within | ||
`<template>`s. Code that relied on this must explicitly walk into template | ||
content documents. | ||
- (*breaking*) Removed `parse()`, `parseFragment()` and `serialize()`. Use | ||
`parse5.parse()`, etc., instead. | ||
- Nodes can be appended to parents with a `null` `childNodes` array. | ||
- DocumentFragments that are appended have their `childNodes` array cleared, | ||
rather than getting a new empty `childNodes` instance. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters