Nathan Whittaker

Thank you for the suggestion, but I think the suitability depends on how you interpret the objective of the addon. It'd be nice to use the addon as a way...

Thanks for the consideration. I was also thinking you could pass in an array of disabled options (similar to how the `selection` attribute passes in an array of selection options)...

I ran into this error when my `` element was inside the shadow DOM of a custom Web Component (specifically Stencil). The height was being computed before the web component...

> `pipe` is a pure helper, it doesn't know anything about it's context other than what's passed in to it. I'm finding that the outer `action` helper will call `pipe`...

> This is actually not accurate. @taras, understood this is not how it's actually implemented. I guess my claim is that the current implementation is less intuitive and leads to...

>...during hot-reload we don't "rerender" component, we removing it, and applying back (count it as a new render, not update) I guess I'm mainly wondering if there's a way to...

+1

There may be some confusion on my part around when an element is considered rendered relative to when it is considered hydrated. I understand if there's no transition when `open`...

I'm using `waitFor()` in the workaround example, but it ends up timing out sometimes. I think what I'm asking is if/can/should DOM interaction helpers (e.g. `click()`) not return until after...

+1. @anhuijhy brings up a good point. Sometimes the initial list may be small. e.g. "Get all the results since yesterday" has no guaranteed length -- but we'd still want...