Perhaps, you chose the wrong approach. Dig in HTML5 data attributes, for examples. That's a better data interface between wikipage code and the View. You can then access them with $(selector).data() method.

>Nevertheless: is HTML5 already in use? If it isn't, when it will be

Perfect! A data- attribute can contain anything and it runbs perfectly. It can contain too a JSON-stringified object added into edit mode into a <span> (so that a while dictionary can be passed into a single data- attribute). It's just what I needed. Alex brollo _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

As I told, I don't know if HTML5 is in use or not; but try to save a <span id="container" data-test="This a test data"></span> into the raw code of any page, then save it, and then use js console of Chrome from the resultin page in view mode with this: $("#container").attr("data-test")

I tried to build a template which wraps template parameters into data- attributes. First results have been incouraging, then I find something logical but unexpected, crushing the whole idea. I wrote into the code of an infobox-like template something like this: <span data-author="{{{author}}}" data-birthdate="{{{birthDate}}}"....></span> and I very happily see that html code had my data wrapped into such span tags. But.... I was testing my code with clean templates, t.i.: templates which have no wikicode into parameter values (as usually occurs into it.wikisource). As soon as I tested my idea into another project (Commons) I found that any wikicode (template call, parameter, link....) present into the value of infobox parameter breaks the stuff, since it is parsed and expanded by parser with unpredictable results. So... I ask you again: is there any sound reason (i.e. safety related,or server loading related ) reason to avoid that HTML comments, wrapped into raw page wikicode are sent back into html rendering as-they-are? Alex brollo

> any wikicode (template call, parameter, link....) present into > the value of infobox parameter breaks the stuff, since it is parsed and > expanded by parser with unpredictable results.

I tried to build a template which wraps template parameters into data- attributes. First results have been incouraging, then I find something logical but unexpected, crushing the whole idea. I wrote into the code of an infobox-like template something like this: <span data-author="{{{author}}}" data-birthdate="{{{birthDate}}}"....></span> and I very happily see that html code had my data wrapped into such span tags. But.... I was testing my code with clean templates, t.i.: templates which have no wikicode into parameter values (as usually occurs into it.wikisource). As soon as I tested my idea into another project (Commons) I found that any wikicode (template call, parameter, link....) present into the value of infobox parameter breaks the stuff, since it is parsed and expanded by parser with unpredictable results. So... I ask you again: is there any sound reason (i.e. safety related,or server loading related ) reason to avoid that HTML comments, wrapped into raw page wikicode are sent back into html rendering as-they-are? Alex brollo _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

2013/1/22 Paul Selitskas &lt;p.selitskas(a)gmail.com&gt; > What do you mean by > >> any wikicode (template call, parameter, link....) present into > >> the value of infobox parameter breaks the stuff, since it is parsed

> >> expanded by parser with unpredictable results. > > If your {{{author}}} doesn't have anything and it's aсceptable, then

> it {{{author|}}}, or {{#if:{{{author|}}}|<span .....}}. Please clarify

Imagine that my infobox had a parameter author=, and imagine a "clean" content as this: author=Alessandro Manzoni With my template code: <span data-author="{{{author}}}"></span> I get into parsed html: <span data-author="Alessandro Manzoni"></span> Perfect! But imagine that my template parameter is: author=[[Alessandro Manzoni]] When I pass the parameter content to <span data-author="{{{author}}}"></span>, I dont' get into html page what I'll like: <span data-author="[[Alessandro Manzoni]]"></span> since wikicode [[Alessandro Manzoni]] will be interpreted by the server, and parsed/expanded into a html link as usual, resulting into a big mess. The same occurs for any wikicode and/or html passed into a infobox

parameter. Alex brollo _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

It will just strip the whole attribute if there is a quote in. That is why we have {{urlencode:{{{1}}}|WIKI}} (or any other mode).

Filed a bug report: <https://bugzilla.wikimedia.org/show_bug.cgi?id=44262>. On Wed, Jan 23, 2013 at 1:34 AM, Matthew Flaschen &lt;mflaschen(a)wikimedia.org&gt;wrote;wrote: > On 01/22/2013 05:24 PM, Paul Selitskas wrote: >> It will just strip the whole attribute if there is a quote in. That is > why >> we have {{urlencode:{{{1}}}|WIKI}} (or any other mode). > > URL-encoding is not the same as HTML-encoding for an attribute. I'm not > sure if we have a parser function for the latter, though.

There will be no mess. You'll just get <span data-author="[[Alessandro Manzoni]]"></span> (did you even lift^Wtry, bro? :)), at least at Wikipedia that is what I get. If it could pass raw HTML into attributes, you'd get a huge hole for XSSploits lovers.

> Is there any sound reason to strip html comments away? If there is no sound > reason, could such a stripping be avoided?

It definitely needs a redesign or a different approach. I believe that putting rendered view into data attributes is the worst practice ever. Data is for data, and if you want to put rendering onto client's shoulders (that is why you want these data attributes, right?), then you should not mix client- and server-site together.