wikimedia
/
parsoid
/
574
/
2
85%
master: 85%
master: 85%
|
Ran
|
Files
70
|
Run time
3s
|
Badge
Embed ▾
README BADGES
|
coverage: 85.879% (-0.002%) from 85.881%
push
travis-ci
Subramanya Sastry
DOMDiff: Get rid of 'modified' diff marker * This was an awkward flag anyway and turns out, it was being added redundantly. * If a diff between node OLD and node NEW wasn't found (even with deep lookaheads in both doms), we were advancing the pointer in the old dom without advancing the pointer in the new dom. This ensured that we'll check for shallow node compares and find improved diffs. In the end, if we run off the end of all siblings in the old dom, we mark all the new nodes as "inserted". However, for some inexplicable reason, we were also adding a 'modified' flag to the NEW node. The 'modified' flag added no new information, but when encountered, pushed selser into a conservative mode. * By removing the flag, it turns out selser is more accurate as shown all the "newly failing" selser tests. I verified about 3 or 4 of these, and in all cases, the selser output is more accurate than before (less dirtying). * Also did some minor comment cleanup. Change-Id: I14d2aaced
11665 of 13583 relevant lines covered (85.88%)
19761.33 hits per line
