After V19 tooltip inside cdk-virtual-scroll-viewport
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- angular, typescript
- Domain
- frontend
Research direction
The report identifies tooltip behavior in cdk-virtual-scroll-viewport after upgrading ngx-bootstrap from v18.0.2 to v18.1.1, but names no source files or tests. Start by reproducing the issue with Angular 19 and a large number of virtual scroll items, then compare tooltip behavior across those versions. Done means identifying the cause and confirming the virtual scroll viewport works with the tooltip.
Written by the indexing model from the issue text.
Description
ngx-bootstrap:v18.0.2 to v18.1.1 and onwards
Angular: v19
Its very easy to create this problem. Use tooltip inside cdk-virtual-scroll-viewport with large number of items
<i [tooltip]="TEST" placement="right" >
its working very fine with v180.2, but if you upgrade ngx-bootstrap to v18.1.1, cdk-virtual-scroll-viewport completely brokes.
I gues tooltip is doing something new in v18.1.1 It may not a bug in ngx-bootrap but as nothing is documented in changelog, i wonder whats changed and whats causing this.
Also i do a complete check on all the commits between this releases but there is nothing changed except converting them to standalone.
This is realy confusing me, what am i missing here and how can it broke it.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from valor-software/ngx-bootstrap
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
valor-software/ngx-bootstrap#6836 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
valor-software/ngx-bootstrap#6834 ·
-
comp(pagination)
Difficulty 1/5 Under an hour Newbie friendliness 76/100
valor-software/ngx-bootstrap#6807 · 4 comments · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
valor-software/ngx-bootstrap#6799 ·
-
Date picker and range picker still accept selection after the form control is disabledPossibly taken @Xapollon430 claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
valor-software/ngx-bootstrap#6839 ·
All issues in valor-software/ngx-bootstrap
Similar issues
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
inabagumi/shinju-date#6823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#540 ·
Maintainers usually reply within 1 day
-
accepted ai-dev ai-implementing
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
livesport/homer#218 · 1 comment ·
Maintainers usually reply within 1 day
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100