3 ms·
I thought his point was clear. A framework provides all those things, free of charge. Instead of using location.href or e.innerHTML you're invited to use framew
by Sacho 10y ago
I thought his point was clear. A framework provides all those things, free of charge. Instead of using location.href or e.innerHTML you're invited to use framework.html(), etc. It's possible you would take care of escaping output on your own, but the point he was trying to convey is that you are likely to take shortcuts and not do all those things.
- MaulingMonkey 10y agoframework.html() would presumably have the same problems as e.innerHTML (as you're probably aware). The examples that come to mind are replacing something like... e.innerHTML = "<td class=\"" + type + ">" + value + "</td>" with: d3.select(e).append("td").attr("class", type).text(value) or: $(e).append("<td></td>").addClass(type).text(value)