Abhishek Hingnikar
Abhishek Hingnikar
@belaviyo You cannot compare the speed of a native program with the speed of a javascript runtime for it . Its never gonna be even comparable.. And there are several...
Now i am confused .. iirc sample rate = number of samples taken in 1 second so to re-construct the audio of 1 second you will need 44.1k samples for...
Seems so, did you create an issue on Chrome Issues? [Adding that for all browsers is a little bit aggressive and might trigger fouc on some browsers]
Pretty sure its better that they fix it since the issue is chrome only.
Cannot reproduce I can scroll just fine, chrome://version ?
@tleunen I think it has to do something with complex structures in chrome (could be userland code aswell). It works in firefox and even edge. There were a few warnings...
That is beyond the scope of this library though as it is a microwrapper.
@tleunen (: have you branched off from being just a micro-wrapper approach?
This could possibly be done by checking the initial offset slightly after first render ?
sure :-) Though can you have a look at my own implementation darkyen/react-ui-components I'd like to know your opinion on the method I chose. (Its heavily inspired by yours)