Tooltip | fit-content support

[rosenthalj]

I'm submitting a ... (check one with "x")

[x ] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Plunkr Case (Bug Reports)
https://primeng-tablefilter-demo-jdhm7o.stackblitz.io

Current behavior
Tooltips that are at the end of a horizontally scrolled table are displayed in a narrow panel approximately one character wide

tooltip.mov

I investigated this issue and found that if I added the following line: this.container.style.width = 'fit-content'; to the end of tooltip class's create method, it appears to fix the problem. I didn't feel I knew the code well enough to create a pull request. Hopefully my investigation will help in determining the "correct" code change.

Expected behavior
Tooltips should be displayed properly whether or not the content of a table is scrolled.

Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/primeng-tablefilter-demo-jdhm7o?file=src%2Fapp%2Fcustomerservice.ts,src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.ts,src%2Fapp%2Fapp.module.ts

I modified the PrimeNG table filter demo as follows:

• I added 3 tooltips to the filter icon/buttons.
• I added a dropdown menu to expand the width of the table.
  -- removed most of the data and removed the second filter table example

To reproduce the problem:

• Run the stackblitz example
  -- https://primeng-tablefilter-demo-jdhm7o.stackblitz.io
• Mouse over the "filter" icon in the last three columns
  -- The tooltips will look correct
• Change the the "Toggle Table Width" dropdown to "Very Wide"
• Horizontally scroll the table to the far right
• Mouse over the "filter" icon in the last three columns
  -- The tooltips will look incorrect. A narrow panel approximately one character wide

What is the motivation / use case for changing the behavior?
fix a bug

• Angular version:
  13.x

• PrimeNG version:
  13.x

• Browser:
  Chrome
  FireFox
  Safari

[cetincakiroglu]

Hi @rosenthalj,

Thanks for your report.
This is an enhancement request so I edited the issue topic.

Regards.