Please add option to remove animation / transition effects in UI

[jessepav]

Describe the new feature and what scenario it helps support:

The fade-in/outs slow down operation of the UI when you're ready to click fast. It would be nice to have the option to remove these transitions.

[mattlag]

Out of curiosity, which animations seem slow? I just checked the CSS, and they are all below 200ms, which is pretty fast to move and click something.

For the update I'm going to release probably today, I made some slight adjustments to the animations to make them more subtle and a bit faster.

I'm still open to this idea, though. Let me know what transitions seem the slowest to you.

[jessepav]

Thanks - the 80ms transition time feels nice.

I played with the app, and found that what I suppose was most surprising to me was not the transition speed of the popover menus, but the mouseout handling, in that

1. Click on a page menu (ex. Page, Editing, or Panel) or top-bar menu (File, Projects, Help), and do not enter the popover region.
2. Move the cursor away from the menu - it does not disappear. This is consistent with browser menu behavior.

However,

1. Click on a menu, move your cursor into the popover region and move it out.
2. The menu disappears. This is different from what I would expect of a popup menu.

What I would prefer is having the menu stay open until the user clicks outside the region or presses Escape, like Chrome popup menus. You're more familiar with usage, though, so if you think that would interfere with a typical workflow, I'll live with it.

[mattlag]

That's slightly older code and I don't remember how exactly it works - but I do remember thinking about all the different ways it could be handled. It could be purely CSS and be instant. I think I use some JavaScript to set a fairly quick timeout when the mouse leaves, but only add the mouse-out functionality after the mouse-over has triggered (the behavior you observe above).

Your suggestion is interesting, because if there is some default behavior that most things use, I'll definitely consider it because 1) it probably has some simple implementation that I haven't considered, and more importantly 2) it feels normal and is what users expect.

I'll put this in the backlog for further investigation. Thank you for the additional input!