-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix safari dropdown not getting closed when click outside #2619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix safari dropdown not getting closed when click outside #2619
Conversation
@lindapaiste Can you please review this PR? As this issue is labeled as "Priority High", we need to fix this issue ASAP. Yes you were right that it's occuring on other components aswell ( fixed in this PR). There is one instance more it's occuring but it's happening on Chrome too, probably someone has raised an issue. ![]() As discussed earlier, we need to stick with one approach of how we are handling outside click throughout our codebase, i think this is the way to go as it's more flexible and with less complications (might work for chrome issues aswell ). Thanks in advance. |
I really don't think that handling it piecemeal component by component is a scalable solution. That's how we get mistakes like the one in your picture where someone put in a menu and forgot to add click-outside handling (yes there is a PR it's #2525). I did look into this more and the components which have the Safari problem don't have explicit outside click handling. They are relying solely on I want us to have one place in the code where we write the logic for outside closing and then use that component or hook in other places. The Which is my long-winded way of saying that in my opinion the appropriate fix for this bug is to merge #2379. @raclim: I know we've talked about giving me authority to approve my own PRs. In the meantime, can you just trust me on this and merge it for me? I know that when I'm refactoring things I'm changing a lot of code and that it's a lot for you to process. But I am writing good code and I'm fixing all sorts of issues like this that go on to reported by someone else months later. |
@lindapaiste Sorry for the delayed response on this! Skimming over it I think so far that makes sense to me and I'm down to merge in #2309 and #2379. There are a lot of changes happening and I could probably be better at getting to them more quickly 😆 but I definitely do trust your process and insight! I'm going to merge in #2649 first and deploy it since the p5.js version just got updated, and then I'll get to merging the other two in. |
Closing with reasons outlined in #2578 (comment)! |
Fixes #2578
Changes:
Same as this, just added the same for
CollectionListRow
componentI have verified that this pull request:
npm run lint
)npm run test
)develop
branch.Fixes #123