@pavish , @rajatvijay , is somebody looking into this issue ?

I'm interested in picking this up

I am interested to solve this issue,Can you please provide some more information?

@sahil-adit you're welcome to work on this. Please submit a PR or ask specific questions. If you have questions about this issue, you can ask them here. Or if you have questions about getting set up with Mathesar development, please ask them in Matrix.

Is this issue still open?

Yes, @abhirupPann this is still open. You're welcome to submit a PR for it.

Are there any more fixes needed. I'm looking for first contribution.

This issue is still open @Mahas1234, feel free to submit a PR.

Is this issue still open? I would like to fix this up. Please assign to me

Yes, this is still open @smit9924. We are preparing for our beta release currently, so some pieces of the app might be broken in the develop branch. Please feel free to reach out on the issue or on one of our Matrix channels if you need help regarding this issue.

Is it ok to work on an issue without it being assigned to you I hope I'll not be stepping on anyone's toes. new to Open Source

@Anish9901 I debug this issue and would like to have some suggestions:
(1) On click the filter button it is common that cell loses the focus and it might be expected as user click the other element out of the table. I don't feel there isn't anything unexpected over there. According to me we should not lock focus on table cell.
Even thought if we would like to implement that then we can add functionality on filter close to shift focus on particular/first cell of the table
(2) On clicking blue border cell shift focus is actually due to border is lies outside the cell. So on click focus is shift to the another cell. This also can be fixed. But what I have observe is focus on cell not looks that much accurate/attractive so one should go the recreating/improving cell focus overall.

Please make your suggestion on above tow points so I can start working accordingly.
Thank you

@smit9924 Please go ahead with option (2) and open up a PR for it, please note that no design changes are required for this. So, please stick to fixing the behavior you described in option (2).

Hey all, I have tried a possible fix for this issue.

Current behaviour

My fix

Before proceeding, I wanted to check: is anyone actively working on this? If not, would it be alright for me to submit a pull request with my proposed changes?

Thanks for your time, and let me know if there's any feedback!

Please submit a PR @sharath-1517.

Please submit a PR @sharath-1517.

Alright, thanks!