Jump to content

Talk:Parsoid/Parser Unification/Known Issues

Add topic
From mediawiki.org
Latest comment: 5 hours ago by IHurbainPalatin (WMF) in topic References from Wikidata not shown correctly

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

[edit]

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)Reply

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

[edit]

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)Reply

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)Reply

Footnote references are not copied

[edit]

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)Reply

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)Reply
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)Reply
[edit]

I checked the page source: these lines of styles for the translate header

border-bottom: 1px solid #a2a9b1;
padding-bottom: 0.4em;
font-size: small;
text-align: center;

got replaced with

font-size: var(--font-size-medium);

Not a huge problem but I lost a heartbeat when the much needed link wasn't where I expected it to be 🤭 Ата (talk) 13:09, 9 August 2024 (UTC)Reply

Interestingly, "This page is a translated version of X" message, placed in the same position but on the translation subpages, renders without change. Ата (talk) 13:23, 9 August 2024 (UTC)Reply
Hi @Ата, thanks for the report! Is this https://phabricator.wikimedia.org/T355664 or another issue? IHurbainPalatin (WMF) (talk) 08:42, 12 August 2024 (UTC)Reply
IHurbainPalatin (WMF), yes, it is the same issue. Ата (talk) 09:16, 12 August 2024 (UTC)Reply
ext.translate.css is missing ABreault (WMF) (talk) 20:50, 12 August 2024 (UTC)Reply

"Issue tracker" not shown in page title line

[edit]

I'm looking at Edit check page and there should be "Issue tracker: #EditCheck" visible to the right of the page title line. Instead it reads Issue tracker: [[phab:tag/{{{1}}}/|#{{{1}}}]]. – Ата (talk) 08:29, 6 October 2024 (UTC)Reply

Hi @Ата, thank you for the report! We're aware of the issue, documented in https://phabricator.wikimedia.org/T348722. IHurbainPalatin (WMF) (talk) 08:36, 7 October 2024 (UTC)Reply
IHurbainPalatin (WMF), good to know! It's hard for me to look for this kind of issues on Phabricator because I'm terrible at tech language, but I still wish to point out what I see, so thanks for bearing with me 😇 Ата (talk) 11:35, 8 October 2024 (UTC)Reply
@Ата We'd much rather have people report existing bugs than not reporting bugs we're not aware of :) And making sure that a given bug is the same or a different one than another one can be surprisingly tricky too. So when in doubt, please let us know :) IHurbainPalatin (WMF) (talk) 11:47, 8 October 2024 (UTC)Reply

References from Wikidata not shown correctly

[edit]

See uk:Карл Бюхер: infobox has some data with references from Wikidata. They are shown with Cite error: Invalid <ref> tag; name "xxx" defined multiple times with different content. Ref name is taken from P248 and url is taken from P854; urls, however, can be different so using P248 for ref name is unwise.
I'm not sure whether that this is necessarily a parsoid error, but it isn't present with the normal settings, and I have no other ideas. Ата (talk) 17:28, 17 November 2024 (UTC)Reply

Thank you for reporting the issue! I filed https://phabricator.wikimedia.org/T380152 to track and fix that. IHurbainPalatin (WMF) (talk) 09:59, 18 November 2024 (UTC)Reply