DataTables / DataTables/FixedHeader
fixedHeader classes when changing absolution/fixed position
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 73
- Forks
- 83
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Hi,
recently I was experiencing problem, that elements in table th and fixedHeader th had different height at very specific window width... I think because of browser rounding in table th to align elements to 2 rows, but in fixed headers elements aligned to 3 rows...
The solution was quite simple, that when fixedHeader is in absolute position is not needed to be visible... https://datatables.net/forums/discussion/15516/display-only-when-table-header-is-not-visible-top-header
But i dont want to modify the fixedHeader file and overriding whole function because of 3 rows of code is quite an overhead.
But it would be really great I think, if fixedheader will toggle some class to differentiate it is with fixed or absolute position. That will allows to hide fixedHeader, if he is absolutely positioned..
My question is, if is planned some posiibility to for example parametrize fixed header to use class, or be hidden when is absolutely positioned?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the reported table-header height mismatch at the specific window width and review the fixedHeader behavior described in the issue and linked forum discussion. Determine how the component distinguishes fixed and absolute positioning, then verify that the requested class or visibility behavior works without overriding the whole function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100