Bug ID: 62025
           Summary: Fix basic selser failures in tests
           Product: Parsoid
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: General
       Web browser: ---
   Mobile Platform: ---


egrep '"selser".* 5", "' ./parserTests-blacklist.js:

add("selser", "Comment semantics: unclosed comment at end 5", "<!--This comment
will run out to the end of the document-->");
add("selser", "HTML-pre: 1. embedded newlines 5",

Subbu: Weird: script passes this test.

Looked into this a bit too, but it does fail reliably in parserTests. The diff
is a newline inside one of the pres. This does not happen in
however. Some issue about non-selser wt2wt mode leaving dirty separator state

add("selser", "Sanitizer: Closing of closed but not open table tags 5", "Table
not started");
add("selser", "References: 5. ref tags in references should be processed while
ignoring all other content 5", "A <ref name=\"a\" />\nB <ref
name=\"a\">foo</ref>\nThis should just get lost.\n</references>");

Subbu: This looks like a real bug that needs investigation and fixing.

add("selser", "Tables: 1d. No escaping needed 5", "foo");

add("selser", "RT-ed inter-element separators should be valid separators 5",
"\n{|\n|- [[foo]]\n|}");
add("selser", "2. Ensure fostered text content is wrapped in spans (traps
regressions around fostered marker on the span getting lost) 5", "\n{|\n|- ||
||\n| a\n|}");

Subbu: Extra leading newline at start of document -- seems harmless, but could
be investigated.

add("selser", "Table in fosterable position 5",

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to