Max

@YurySolovyov what usability problems do you see? I'd argue that it's even more usable since the clickable area is larger! :)

I don't think that's a problem if it's an optional feature! once a user chooses to enable waveform seek bars in the settings they surely anticipate that something will change...

updated [the gist](https://gist.github.com/bodyflex/e4f6c9ec0fdea9450fd9303dd088b96d) now. it plays music with an `` element and visualises the progress on the waveform. you can also skip around the track. @KeitIG at this resolution, SVG...

 just so you know: you only need to save that gist in an HTML file and open it (in Chrome). it should work...

@talaviram at least FabFilter's Pro-Q3 seems to work even after resizing it

just ran into this, would be awesome if you could use `classList` with styled components! it's oftentimes much more convenient than to pass in and handle a custom prop in...

@abeikverdi could you provide an example project where this is happening?

wondering if the problem actually lies within nih_plug: the VST3 [`onKeyDown` implementation](https://github.com/robbert-vdh/nih-plug/blob/master/src/wrapper/vst3/view.rs#L343-L350) returns `kResultOk`, but according to the [API docs](https://steinbergmedia.github.io/vst3_doc/base/classSteinberg_1_1IPlugView.html#a759b576f046e699c84dc07d579600b1b) it should return either `kResultTrue` or `kResultFalse` depending on whether...

returning `kResultFalse` from the VST3 key handlers indeed allows the key events to flow to the plugin (this has been fixed in nih-plug now https://github.com/robbert-vdh/nih-plug/commit/245add6530f1c7d83fea5e23636145d982af4d66)! but now the problem is...

what's the status on this one? 😕