Talk:Parsoid/Parser Unification/Known Issues

I found an issue when using Parsoid to read an article or discussion

Use this topic to discuss or report an issue you've found when using Parsoid to read an article or discussion page. Please check the known issues list first to ensure we don't already know about your issue! cscott (talk) 01:43, 15 November 2023 (UTC)

• @Cscott: Reference previews don’t work on https://hu.wikipedia.org/w/index.php?title=Sablon:Spanyol_telep%C3%BCl%C3%A9s_infobox&useparsoid=1. Article previews work, reference previews with the legacy parser work. Tested logged-out to make sure it’s not caused by NavPopups (which also provides reference previews). —Tacsipacsi (talk) 19:46, 18 February 2024 (UTC)

  Thanks for the report! Filed as T358242. cscott (talk) 16:19, 22 February 2024 (UTC)

  @Tacsipacsi I see reference previews working on a number of article pages. So, I think you are saying it isn't working on *this* page or the Template namespace? If you know anything more about the scope of this breakage, that will be helpful and save us the trouble of digging everywhere. But, otherwise, we'll take a look. Thanks! :) SSastry (WMF) (talk) 17:15, 22 February 2024 (UTC)

  @SSastry (WMF): Yes, I wrote and meant that it doesn’t work on that specific page, because I didn’t test it anywhere else. Thanks in advance for looking into it! —Tacsipacsi (talk) 14:37, 23 February 2024 (UTC)

  I updated T358242. Looks like reference previews generally don't work with Parsoid HTML -- it is probably an exception that it works on huwiki main namespace. Will take a look. SSastry (WMF) (talk) 18:24, 8 April 2024 (UTC)

  These work everywhere now, but the reference previews are slightly different from legacy ... the content selection code in the reference preview code probably needs an update for Parsoid's cite output. The difference is especially obvious for named references, unless of course the new output is the preferred version. :) SSastry (WMF) (talk) 13:08, 19 April 2024 (UTC)

Parsoid has trouble with Template:code documentation on en.WP

Compare https://en.wikipedia.org/wiki/Template:Code?useparsoid=1 (very broken) and https://en.wikipedia.org/wiki/Template:Code?useparsoid=0

The latter renders fine, although many Linter errors are reported by LintHint in the rendered-page mode. LintHint does not report any error in Preview. This may be a GIGO situation that LintHint can't handle in Preview, and that causes Parsoid to expose a subtle syntax error. Jonesey95 (talk) 16:22, 6 March 2024 (UTC)

Strangely, I was able to resolve both the Parsoid problem and the Linter problem with this edit. I don't see anything technically wrong with the previous code, though. Someone might want to copy the old code into a sandbox to test it. Jonesey95 (talk) 16:29, 6 March 2024 (UTC)

Footnote references are not copied

Because footnote references are implemented in CSS, they don’t get copied when copying the article text. Try copying https://hu.wikipedia.org/w/index.php?title=Teemu_Keisteri&useparsoid=0 and https://hu.wikipedia.org/w/index.php?title=Teemu_Keisteri&useparsoid=1 to a word processor: the footnotes themselves are copied from the bottom of the article, but the inline references are missing. This has a serious negative impact on certain Wikipedia content reuse scenarios (e.g. copying the article to a word processor for offline access, or to start creating a derivative work). —Tacsipacsi (talk) 15:57, 17 March 2024 (UTC)

Interesting. The inline refs aren't generated via CSS -- only updated via CSS post-load. The HTML does contain the inline refs in English (as default). So, curious what is causing them not to be copied. Needs investigation. SSastry (WMF) (talk) 19:33, 24 March 2024 (UTC)

I see the reference in two forms:

• a <span> with display:none – doesn’t get copied because of this CSS rule;
• an ::after pseudo-element with content: "[" counter(mw-Ref) "]" – doesn’t get copied because it’s not a real element.

I haven’t checked the source code before, and assumed that it’s CSS-only to allow out-of-order parses (which don’t know yet what number will be assigned). If it’s not the cause (the <span> contains the number, so it seems it’s not the cause), then why can’t it work the same way as in the legacy parser? —Tacsipacsi (talk) 22:09, 24 March 2024 (UTC)