zeroinformatique

Same issue here, with an additional note: On Android/Chrome, the dragscrollstart event is triggered almost instantly, making it difficult to guess if we're on a click (touch) or a real...

```js export default class DragScrollClickFix { readonly DRAG_DELAY = 100; // This is the minimal delay to consider a click to be a drag, mostly usefull for touch devices timer:...

v1.10.2 here. Didn't test it on 2.0.0.

Just tested, issue is still present in v2.0.0 Edit: and my fix still works.

Child. You dragscroll the parent, using your mouse or touchscreen. When you release the drag, it triggers the click on the child component which is beneath the cursor or finger.

I noticed the power isn't draining when you are away from your probe. So, as long as you don't switch to your probe, it's working indefinitely. Is it possible to...

A first step, without all this complexity, would be to make sure the power generation is positive when leaving the vessel. Otherwise it doesn't really make sense to fine tune...

A very simple way to do it in TypeScript: ``` @Ref() readonly content!: Vue; // Points to your scrollable component scrollPositions: { [index: string]: number }= {}; @Watch("$route") routeChanged(newRoute: Route,...

Isn't it easier to simply display a warning if the root part gets staged during the simulation, and stop the simulation at this level? Giving wrong numbers is a lot...

I was actually looking for a plugin to do exactly what Guillaume suggests here. The solution could be to declare where the plugin stores its Notes (instead of Eclipse Repo),...