On 11/05/2014 01:21 AM, Federico Leva (Nemo) wrote:
Subramanya Sastry, 04/11/2014 23:05:
If someone does take this up, based on this morning IRC's discussion,
the following steps would be useful:
* Pick a specific browser, say, Chrome (to eliminate any browser-bug
related issues)
* Install the gadget by Jackmcbarn that lets you look at parsoid html
for a page
* If there is a diff seen, use the visual diff service to generate a
visual diff for the page
* Use the visual diff to find the root cause of the diff and report a
bug (if it is not already known).
One of the issues you are likely going to run into is: (a) find diffs
because of known issues (b) find diffs that are all caused by the same
newly reported underlying issue.
Thanks. This sounds like a very good definition of a task, so I've
appended it to the previous list of candidate tasks:
https://www.mediawiki.org/wiki/Talk:Google_Code-in#Parsoid_bugs
It can be polished there and will certainly come handy sooner or later.
Thanks. Added links to the two bullets that needed it.
Subbu.
_______________________________________________
Wikitext-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
