Lennart Hildebrandt

I agree that this method is missing. I also thought about using `model.clear()` and `model.set()` in conjunction. Then I ran across the problem, that I trigger the `change` event twice...

No, this does not help. Imagine you a have a key `foo` in the current attributes hash of the model, which is not present in the new `attrs` hash you...

Quite unpleasant bug when working with Mobx and TypeScript. I'm currently working around this by setting the property directly and ignoring the typescript error for now: ``` // @ts-ignore instance.foo...

I can confirm this. Both with a `Remix` and `vitest` setup.

You're saying there is a reason why devices are listed for some browsers and some not? I was wondering. Why for example has Servo listed all devices possible with WebVR...

Ah, I see. Thanks for the quick response.

I had trouble with the cell height when Flickity was initialised. Added a little `setTimeout` which fixed this: ``` js Flickity.prototype._createResizeClass = function() { setTimeout(() => { $(this.element).addClass('flickity-resize'); }); };...

> Having all items be position: absolute makes it easier to move them around for wrapAround behavior. @desandro What about `order`?

@desandro True. Run into many quircks myself with flexbox. What about setting the height of the cells instead? Wouldn't that fix the problem somehow? Not as elegant as setting the...

Yeah, that seems to be a bug. I will take a look at this as soon as #105 is deployed.