keys
on, like maybe onto or something.
onsubmit or onclick to Object.prototype?
Object.create(null) differently.
{}, that is.
Has anybody run into an issue with TypeError: null is not an object (evaluating 'node.parentNode') ONLY on safari or iOS browsers?
I don't get that issue on chrome
onchange vs oninput for the input components
@Brianhasagithub BTW, you could start migrating some of that by downloading v2 as a separate module (like adding "mithril-v2": "npm:mithril@2.0.4" as a dependency) and migrating to its hyperscript, creating a wrapper that's basically this:
var v2 = require("mithril-v2")
module.exports = function m() {
var vnode = v2.apply(undefined, arguments)
// Re-add an internal property removed in v2
vnode._state = undefined
return vnode
}That could get you the checking half, so you can phase it in incrementally.
hmm.. on a quick glance it seems very computer sciency in the ember way..
This exactly. It's like a really crap version of @JAForbes stags
@panoply
Just had a 20 minute conversation with a potential client who wanted a React application purely based on the fact it's a "Facebook product" – Interestingly this individual knew nothing about tech. They founded a fashion brand (rather successful one too if you know clothing). When I queried as to how they had heard of React (before declining the project) they told me that they had read about it on a tech website. My ears spiked when they told me this and asked if they often read tech websites....
"Oh not at all, just an article I found on Facebook"
LOL truth
