-
-
Notifications
You must be signed in to change notification settings - Fork 333
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
fixed popup not being able to find the correct target because client side rendering hasn't finished yet #2466
fixed popup not being able to find the correct target because client side rendering hasn't finished yet #2466
Conversation
…side rendering hasn't finished yet
… client side rendering hasn't finished yet" This reverts commit 2926ce4.
…side rendering hasn't finished yet
🦋 Changeset detectedLatest commit: 756ed72 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@TheEisbaer just FYI we've technically put popups into a feature freeze as we prepare for Skeleton v3. We plan to handle these very differently in the future. That said, I will make an exception since this looks to be a good fix. However, just note it may take a while for me to get a proper review in. Just wanted to give you a heads up. |
Hey @TheEisbaer, unfortunately I am not able to accept your PR as I'm having trouble replicating the original issue as described. In #2465, you mention that having a nested child layout and popup triggering within that, but it fails until you refresh the page. I can see this happening in your linked app on Stackblitz, however I cannot replicate it in a minimal reproduction (keyword: "minimal"). I'm sharing it here in case you wish to test it as well: To run it:
While I understand your app is not in a functional state, the issue with sharing your full application is it makes it much harder to isolate where things are going wrong. It could be some unforeseen combination. I'd encourage you to compare your code to mine and see if you can isolate the fault. Until then I'm going to close this PR, but will gladly reopen or consider other PRs if you can help showcase where the issue occurs. Thanks. |
@TheEisbaer my apologies for now getting back to this sooner. I've just been snowed in with other projects. While I think your change is good, there's a couple things I'm taking into consideration right now:
Given all this, I think the best way forward is going to be to put this on ice for now. It's not that it's a bad or wrong change or implementation, mostly just bad timing to be honest. If you need this change, I suggest forking the feature and implementing locally, assuming you haven't already. That or try this work around. FYI I'll be making a public announcement next week that I'm shifting the majority of effort from v2 -> v3, so this will likely make sense under that context. Either way, thanks for the contribution. |
Linked Issue
Closes #2465
Description
My attempt at implementing a mutation observer as mentioned in the issue
Changsets
Instructions: Changesets automate our changelog. If you modify files in
/packages
, runpnpm changeset
in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should beminor
while chores and bugfixes should bepatch
. Please prefix the changeset message withfeat:
,bugfix:
orchore:
.Checklist
Please read and apply all contribution requirements.
dev
branch (NEVERmaster
)docs/
,feat/
,chore/
,bugfix/
pnpm ci:check
pnpm format
pnpm test