Page MenuHomePhabricator

Value-less extension attributes not preserved
Open, MediumPublic


<syntaxhighlight strict lang="php">$foo</syntaxhighlight>

round trips to

<syntaxhighlight strict="" lang="php">$foo</syntaxhighlight>

Either Parsoid needs to fix this, or we need to tell extension authors that attributes must have values (as per XML).

Event Timeline

Esanders created this task.Jun 9 2015, 3:20 PM
Esanders raised the priority of this task from to Needs Triage.
Esanders updated the task description. (Show Details)
Esanders added a project: Parsoid.
Esanders added a subscriber: Esanders.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 9 2015, 3:20 PM
ssastry triaged this task as Medium priority.Jun 9 2015, 3:23 PM
ssastry set Security to None.

Implementing this would be a little problematic for VE too, as we use a XML builder to generate the wikitext for updating the rendering. We'd probably have to switch to sending over the Parsoid HTML and having the API round-trip it to update the rendering.

ssastry added a subscriber: ssastry.Jun 9 2015, 3:48 PM

A few questions come to mind:

  • Does the dirtying affect the semantics of the tag extension? Or is it just a noisy dirty diff?
  • If the latter, and if only a handful of extensions are affected, we could make a case for tag extensions to be xml-compliant and then use a bot to fix up.
  • If semantics are affected and/or a lot of extensions use these kind of properties, it will take more work.

I suspect not many extensions use this, and even fewer would have a flag attribute that could also be a value attribute. That said, <syntaxhighlight> claimed in documentation that using 'line' without a value was equivalent to the default value, line="FACNY_LIES", although this was all lies and the php only cared about the presence of the attribute (see ).

Without doing a full audit of extensions I couldn't say for sure if there are any other instances.

I think a dirty diff of attr to attr="" will annoy users though, so if we do go down the XML route, we should have a default value for booleans, e.g. ="1"

The problem with requiring a value is that ="" looks messy in the source and="1" may confuse users into thinking that ="0" will disable the feature, while many extensions are coded to just check for attribute existence.

cscott added a subscriber: cscott.EditedJan 3 2019, 10:39 PM

I think HTML5 says that an empty attribute is actually itself, not the empty string? (Let me check...)

Alas, "empty attribute syntax" is one of the things which changed between XML, HTML4, SGML, and HTML5. And wikitext extension tags are not any of those, really, so of course we don't have to match them exactly. But it would be nice to move to the HTML5 semantics, just to reduce surprise.

Parsoid should probably just serialize empty attribute values using the empty attribute syntax, since that's almost always what's wanted. That would take care of most of the dirty diff issue. Of course, we could/should tweak the PHP side API to use the HTML5 semantics (that is, treat empty attribute syntax and the empty string value as identical, as far as extension code can tell).

Please provide me with an update? Are you working on it?

LGoto moved this task from Needs Triage to Backlog on the Parsoid board.Feb 15 2020, 9:43 PM
LGoto moved this task from Backlog to Bugs & Crashers on the Parsoid board.Jun 18 2020, 6:14 PM