Possible bug on Column Filtering
Possible bug on Column Filtering
dlopezz
Posts: 5Questions: 1Answers: 0
Hello guys,
While checking this example:
I saw that there's a bug. Details:
- Put string "Acc" in Position column and you will get the new table with the search (2 rows).
- When you try to select the text in a row with the mouse (dragging with your mouse) you won't be able. You will have to select the text a second time for it to work properly.
This is awful especially if the row has a link, so the users will have to click the link twice.
Is there any solution for this?
Thank you in advance.
Answers
Yep, I'm seeing that too, it happens when the table is slightly scrolled. We'll take a look and report back - thanks for letting us know,
Colin
Looking forward for the solution. Thank you.
Interestingly it is a Chrome / Blink only issue this - doesn't happen in Firefox.
Change the event listener to be:
I've committed the fix here. Thanks for flagging this up.
Allan
This change solves the "dragging the mouse over the text" problem, but the bug still happens when clicking links contained in the table.
Live example
The same:
Users will have to click the link twice.
Is possible to solve this?
Thank you in advance.
I have trying some changes but it still happens.. Any clue to solve this?
Solved.
If anyone face this in the future, the solution is to use the Javascript code from this other example:
FixedHeader example
Thank you.
Interestingly, that approach only works with an older version of FixedHeader. With the current version the focus is lost as soon as you type into the input element (which is what all that range setting code is about).
I think we probably need to go back and check the range selection code to understand why it is messing up selection in Chrome.
Thanks,
Allan