Lev Chelyadinov

@BinaryMuse Thanks, I see what you mean. Will it be a performance hit to recreate the button (and bind the event handler) every time a new row is appended? And...

@BinaryMuse can you please elaborate? The README has no examples of using keys (which are badly needed btw). I'd love to see a code sample. And the thing is, the...

Consequently, the same problem occurs with `Infinity` and `undefined` as the default values for a prop, as those are global _variables_. It is also spotted with components and other Svelte...

I would be willing to implement this feature with some guidance

The Atom community (me or someone else maybe) is willing to make a PR to implement these changes if there's a green light from the core Atom team.

@rsese Guess my lies are uncovered now - I really did not expect a package to cause such an issue so I didn't bother trying Safe Mode, but guess what...

@rsese actually, looking more into this problem and ways to solve it, I've stumbled across [this line of code](https://github.com/atom/autocomplete-plus/blob/master/lib/autocomplete-manager.js#L188) in `autocomplete-manager.js`. It turns out that `autocomplete-plus` watches a config of...

@Chinwike1 the problem is: the dropdown is closed when the document is saved, unless it was an autosave made by [this](https://atom.io/packages/autosave) package (which is bundled with Atom). So the way...

Yeah, you'll have to code these yourself. Attractions does ship with some media queries to adapt the components to screen sizes, but custom adaptation logic will have to be coded...

Could you please provide a reference as to why that makes the component more accessible? To my knowledge, this change has the opposite effect