Last modified: 2013-07-04 10:33:21 UTC
As per Subbu's report. (The corrupted table is going to be a different bug.)
I get a JS error when trying to preview the diff in that page using FF: [13:44:04.016] Error: toDomElements() failed to return an array when converting element of type alienBlock @ http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130506T190432Z&*:130
(In reply to comment #1) > I get a JS error when trying to preview the diff in that page using FF: > [13:44:04.016] Error: toDomElements() failed to return an array when > converting > element of type alienBlock @ > http://bits.wikimedia.org/en.wikipedia.org/load. > php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext. > visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs. > wordbreak&skin=vector&version=20130506T190432Z&*:130 Bug 48181.
Can you link to the original report?
(In reply to comment #3) > Can you link to the original report? The midden of bug 47712.
Those were FF-specific, which points to client-side issues. Are they now an issue independent of the browser?
(In reply to comment #5) > Those were FF-specific, which points to client-side issues. Are they now an > issue independent of the browser? Actually, that bit wasn't FF-specific, it was happening in Chrome as well (and I can confirm that it still does).
I am still getting a clean diff with Chromium (and &debug=true to work around current VE breakage). Can you point out any pages that have a dirty diff both in FF and Chrome?
Related URL: https://gerrit.wikimedia.org/r/62546 (Gerrit Change If16dda01058715acee8df347b2b9c4da84609113)
Fixed in production.
[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704]
