[Tooltip] Change `disableInteractive` default value

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

After a tooltip is shown, moving the mouse cursor over the tooltip keeps it open indefinitely. It is hidden only when the mouse cursor is moved outside it.

Expected behavior 🤔

The tooltip should close as soon as the mouse moves outside the main element. This is illustrated in the Material Design guidelines: Also, the statement “Continuously display the tooltip as long as the user long-presses or hovers over the element.” implies that when this is no longer the case the tooltip should disappear.

See other Material Design implementations for comparison, e.g. Vue/Quasar), does it correctly:

Steps to reproduce 🕹

To reproduce:

1. Go to the built-in example).
2. Move the mouse cursor over the IconButton: The tooltip is shown.
3. Move the mouse cursor outside the IconButton and over the tooltip. The tooltip is still shown. It is hidden only when the mouse cursor is moved outside it.

Context 🔦

Any context / all uses.

Your environment 🌎

`npx @mui/envinfo`

``` Browser: MS Edge v. 97.0.1072.69, 64 bits System: OS: Windows 10 10.0.19042 Binaries: Node: 14.15.0 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 97.0.4692.99 Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.69) npmPackages: @emotion/react: ^11.7.1 => 11.7.1 @emotion/styled: ^11.6.0 => 11.6.0 @mui/base: 5.0.0-alpha.66 @mui/material: ^5.3.1 => 5.3.1 @mui/private-theming: 5.3.0 @mui/styled-engine: 5.3.0 @mui/system: 5.3.0 @mui/types: 7.1.0 @mui/utils: 5.3.0 @types/react: ^17.0.38 => 17.0.38 react: ^17.0.2 => 17.0.2 react-dom: ^17.0.2 => 17.0.2 ```

[leosdad]

Hi, OP here. Thanks all for the responses and the workaround, although I can’t test anything because I’m on vacation now. I’ll comment further when I’m back. Cheers

[eps1lon]

@ggascoigne As far as I can tell, this issue is about interactive/disableInteractive which isn’t related to the accessible name/accessible description. So if there’s an issue with describeChild, I would recommend opening a separate issue.