Florian Cargoët

I hit the same problem. In my case, the best fix is simple: do not round the percentage.

If I find some spare time, I'll try to implement it and send a pull request.

I'm working on that. I've some questions if you're still interested in that feature: - syntax of the comment ( // cover:false ?) - should it only ignore one line...

- Being on an ignored line, `foo` would be ignored. - Being on an ignored line, the assignment to `bar` would be ignored. - Being inside a syntax tree started...

Here's the pull request. Hope you like it. About the commit access, let's first see if I come up with other fixes/features ideas.

It's happening to me today… Fixed by restarting Chrome entirely, devtools restart or incognito mode weren't enough.

Si je comprends bien, tu voudrais conserver le mécanisme actuel (table en sticky quand elle arrive en haut de l'écran) et ajouter un comportement particulier tout en bas de page...

I have the same issue.

My workaround is to use a react ref which I always update. In the click handler, we have access to the latest value with ref.current.

The fade animation does set the opacity to 0 itself in its `added` function so removing it from Element.added does not break "fade" but fixes "none".