-
## todos
- [ ] cache elements (#250)
- [ ] switch off `morphdom` to `nanomorph` (https://github.com/yoshuawuyts/choo/issues/152)
---
## Issue
Looks like doing renders in quick succession means …
-
Would it be possible to see some performance metrics, how its better than normal DOM manipulation?
https://developer.mozilla.org/en-US/docs/Web/API/Performance_API
farzd updated
7 years ago
-
## Bug Report
This could be a morphdom issue.
### Context
```jsx
class {
onCreate() {
this.state = { width: 200, height: 100, color: "blue" }
}
choose(e) {
this.state.colo…
-
Do we think we should copy input values ala `yo-yo`?
Always felt weird to me that `morphdom` doesn't handle this case.
-
If this library becomes a thing we would probably want to keep parity with the `nanomorph` diffing algorithm or (`yo-yo` if they're not keen). It would be cool if we could create a shared testing libr…
-
When using [appendChild](https://developer.mozilla.org/en-US/docs/Web/API/Node/appendChild) to add children from the new tree to the original it removes them from the original.
Should we add a warnin…
-
I'm currently trying to work out how to call `.focus()` on an element.
``` js
const yo = require('yo-yo')
function textarea (value) {
const el = yo`${value}`
el.focus()
return el
}
const foo …
-
-
Currently, Marko supports "scoped IDs" in the form of a "ref":
```html
OK
Cancel
```
A nested element/widget can be looked up by a ref:
```js
var okButton = this.getEl('button');
…
-
There is a `skip()` method in the Incremental DOM, which tell the renderer to skip node children render. It's good for a "poor man" web component w/o shadow DOM, slots etc... So basically you move res…