=== wallyworld_ changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer:wallyworld | Firefighting: - | Critical bugtasks: 4*10^2 [00:10] Mmmm, readable loggerhead [00:10] A nice change. [00:11] I did wonder if a NDT would update loggerhead [00:11] Still needs to be degnomed a bit more [00:11] But much better [00:41] is it just me or does the 'add an attachment' link on bugs now lose the text you already entered? [00:44] wallyworld_: yes [00:45] lifeless: cool. cause i was thinking we would have a standard set of helpers to do the equivalent of out standard tal formatters for person etc [00:46] you'd probably use partials for that [00:46] * wallyworld_ hasn't read the doco yet [00:46] helpers should be used when you need host language logic [00:46] partials should be used when you want to reuse a template elsewhere [00:46] ok [00:47] {{> person assignee} [00:47] for instance [00:47] i am thinking about the +sharing view [00:47] bah, }} at the end, but you get the idea [00:47] for now, i might just hard code the formatting [00:47] {{> }} [00:48] lifeless: is it on anyone's todo list to do the handlebars bundling? [00:49] so, handlebars is in yui3.5 [00:49] I imagine rick or deryck are likely to step up and do that [00:49] Blocked on combo loader [00:49] ah, cool. but i guess we need something to use till then, or we can wait [00:49] indeed [00:49] you can use mustache now (and pystache || pybars on the server) [00:50] it's just prototyping atm so will do [00:51] pystache has some wtf's apparently :) - pybars is in the download cache, if you wanted to play with it and tell me what you think [00:51] lifeless: i was looking to do the rendering on the client [00:51] wallyworld_: oh sure [00:52] lifeless: still, server side vs client side rendering is something that needs some thought etc [00:52] one argument is that all rendering should be done client side [00:52] after getting json data from the server [00:52] wgrant: Is qas's database back to FK goodness? [00:53] s/from the server/using the api [00:54] wallyworld_: you have been following the thread on that right ? [00:55] StevenK: No [00:55] wallyworld_: there is a proposed standard for us [00:55] StevenK: Hopefully tonight. [00:55] lifeless: i was about to re-read it, i think it was advocating getting as much stuff from the api as possible [01:07] if you use innerHTML with something containing a script section, does that script section run ? [01:11] lifeless: don't think so, not in a consistent and portable way [01:12] lifeless: if you need it i would claim the design is broken [01:12] wallyworld_: its the reverse, I'm assessing some security risks [01:13] in our stuff? [01:13] it would terrify me if it worked ever [01:13] it can be made to work [01:13] for not in a portable way afaik [01:13] if it ever works, thats sufficiently terrifying [01:14] lifeless: one example, possibly old, for ie, you can mark a script tag with DEFER and it will execute when set vua innerhtml [01:15] not sure if that's still the case, ymmv etc [01:15] what i'm saying is people have found ways to do it i think [01:17] sure [01:17] -> it means folk /wanting/ it to work can probably do so, but folk can't (and shouldn't rely on it just working [01:17] yes [01:17] and we should actively discourage/forbid it :-) [01:18] lifeless: How is that terrifying? [01:18] it also means that folk which want to us js to customise delivered html to another site, can't reliably do so (and those sites would be crazy to accept it) [01:18] wgrant: its off-site js all over again [01:18] ...., yes that's why you don't use innerHTML [01:18]