Ran
|
Files
152
|
Run time
7s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/wikimedia/parsoid/commit/72aa95a55">DOMHandlers: JS undefined-vs-null distinction doesn't work in PHP * Unlike in JS, in PHP, we cannot distinguish between undefined and null in return values of functions. Ideally, we shouldn't have relied on that distinction in the first place. * All except the EncapsulatedContentHandler were yielding the next sibling of a node to process. So, explicitly return the next sibling or the node to process in all handlers. * Cleaned up the documentation for DOMHandler::handle as well as got rid of Feb 2013 era code in SerializerState::serializeChildren that handled traversal of children. Change-Id: I</a><a class="double-link" href="https://github.com/wikimedia/parsoid/commit/0981e0f01">0981e0f01</a>
9530 of 12004 branches covered (79.39%)
14903 of 17618 relevant lines covered (84.59%)
29647.44 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|