| thiemowmde moved this task from incoming to needs discussion or investigation on the Wikidata board. thiemowmde assigned this task to hoo. thiemowmde added a project: Wikidata-Sprint-2016-10-11. thiemowmde added a comment. |
Since this ticket was created, a product manager decision was made: @Lydia_Pintscher listened to all the arguments we (mostly @hoo and myself) collected and said ok.
My main argument is: Having this new parser function always return an HTML element, even if the content of the HTML element is pure text, does make it 100% obvious what this parser function is about. You get HTML, and should not escape it or process it further. If a user does not want this, he should use the existing {{#property:…}} function.
Rather than talking about a <span> element I would phrase the guarantee we give as follows: "Guaranteed to be a single HTML element node, possibly containing text and other HTML nodes." This gives us the freedom to choose whatever element is appropriate per value type. Monolingual strings become <span lang="…">…</span>, but item references become <a href="">.
The guarantee is relevant when feeding such strings to HTML parsers and such. For example, jQuery( '1 <span>m</span>' ) fails, but jQuery( '<span>1 <span>m</span></span>' ) is fine.
If we agree on this, I believe we can close this ticket as resolved.
Cc: Izno, Aklapper, Lydia_Pintscher, daniel, aude, Lucie, thiemowmde, hoo, D3r1ck01, Wikidata-bugs, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
