Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Angular Material Tooltip stop working after virtual scrolling
See original GitHub issueI’m submitting a … (check one with “x”)
[ x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter
Current behavior When one of the datatable cells contains an Angular Material2 Tooltip component, it will stop working after the user scrolls (the datatable is configured with vertical virtual scrolling). When this happens, you can see a blank tooltip shows at the top left corner of the page.
Expected behavior Material Tooltip should always work regardless the user scrolls or not
Reproduction of the problem
- Browse https://stackblitz.com/edit/angular-mq8vbn
- move the cursor over the 1st column cell values, you should see ‘Hello World’ tooltips
- now scroll down several rows
- move the cursor over the 1st column cell values, this time the tooltip won’t work.
(I suspect it might be a zone issues)
What is the motivation / use case for changing the behavior? It breaks the tooltip
Please tell us about your environment: N/A
-
Table version: latest
-
Angular version: 5.0.0
-
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
-
Language: [all | TypeScript X.X | ES6/7 | ES5]
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 We are also seeing this error happening when using the datatable. I manually removed the runOutsideAngular wrap which fixed our problem.
This seems to be the root cause for about a dozen zone / change detection-related problems in the issues list. Really surprising that this hasn’t been fixed - the problem has been there since before Christmas and I’ve had to keep using v11.0.4 since then as a result.
Is this project still actively maintained and will it ever be fixed? I hope the answer is “yes” to both as it’s a really useful datatable, but the way things are going it might be time to switch to something else…