Something like http://example.com{{deadlink}} cannot be properly edited in VisualEditor. It should be processed as two pieces: one external link that is followed immediately by one template. Instead, it is presented as the text "http://example.com[]", linked to http://example.com[].
Description
Description
Details
Details
- Reference
- bz65362
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T67362 VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited | |||
| Resolved | Feature | None | T63969 VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder |
Event Timeline
Comment Actions
Caused by mw:ExpandedAttrs from Parsoid.
Input:
| http://example.com{{deadlink}} |
Output:
<a data-mw="…" typeof="mw:ExpandedAttrs" about="#mwt2" rel="mw:ExtLink" href="http://example.com" data-parsoid="…">http://example.com</a>
Comment Actions
Supposedly the reason for this is that http://example.com{{echo|/index.php}} would produce a link to http://example.com/index.php , rather than a link followed by text. But it depends on what the template outputs; if the output starts with a space or a newline this won't happen. Maybe Parsoid is being a bit too trigger-happy with mw:ExpandedAttrs in the second case?
Comment Actions
URLs followed by templates are still broken. However, they now seem to be broken differently: they display as regular links with broken syntax, rather than as alienated nodes.