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
Frame issue #407
Comments
Hi @Sahak885 - could you please confirm
Thanks! |
|
I encountered the identical problem following the library upgrade too. |
|
Got the same issue
|
Thanks all! I'm struggling to reproduce. Would someone be able to provide me with a repo that reproduces the issue? |
Thanks @Sahak885 but I'm looking for a code example (GitHub repository) that reproduces the issue so I can debug it. The error message makes it look like an environment issue, but I'm not sure what's triggering it. |
Thank @chrisvxd for your answer. I can send you our package.json file. You can check versions and try to debug it
|
Hi @chrisvxd, to reproduce the issue, here's an example:
When using this code in the Puck editor component, an error occurred |
Repository: https://github.com/Sahak885/puck-editor-frame-issue |
Thanks for the reports. I think I know what's going on. Our underlying dnd fork (@measured/dnd) is not discriminating between the Puck iframe and other iframes. The other iframes exist on other origins, which is causing this security issue. Will patch @measured/dnd. |
Would someone mind confirming if this is resolved in |
Reopening until fix confirmed |
@Sahak885 looks like a new issue. Again, I cannot reproduce. Can you please provide an example of how to reproduce this new error? |
When I try to open editor I get this error. I think it comes from new iframe functionality |
@hrachgalstyan that's a new error message, but same as @Sahak885 . The previous one was a security warning. I could really do with a code example to reproduce, but I'm going to try something else to tighten it up and see if it helps. |
The previous one seems to work |
I've pushed a potential fix and republished again. Please try again in the latest canary 0.14.2-canary.2b2ef32 |
Is it the latest version? |
0.14.2-canary.2b2ef32 is the latest version. You have to explicitly install it (i.e. put |
It loads very hard |
Hi @chrisvxd , Repository updated with the following:
Regarding the second issue, when I click on items, the system automatically assumes I want to drag them. Thanks! |
Thanks @Sahak885. The second issue has been fixed in the latest canary, but I'll dig into the slow load now. |
Is the second issue fixed in this version @measured/puck@0.14.2-canary.e6e01c6? |
@Sahak885 I believe I've also fixed the slow load issue when dragging the item into the page. Please note, this is different to the issue you reported the other day. I've tested and it seems to be working in
Please test the fix and report back if it addresses your remaining issues. |
Hi @chrisvxd, Regarding the first issue, it's still running slowly, but you can find the updated video on Loom here. Thanks! |
Hi @chrisvxd , May I verify the issue? Which version are you referring to? |
Hi @Sahak885. I believe the latest canary |
In this version, the iframe doesn't show. |
@Sahak885 😭 any console logs or anything? I'm unable to reproduce that in your example repo. Kapture.2024-04-16.at.08.03.25.mp4 |
I have updated the repository. Should we pull the changes? |
Could you please run |
This issue occurred in production mode. To reproduce:
|
@Sahak885 no need to pull the changes - they have significant improvements. Thank you so much for the reproduction steps. I was able to reproduce, and this should be fixed in The last thing is the slow auto-scroll (auto-scroll enables the frame to automatically scroll whilst dragging at the edges of the viewport). This is complex to fix, and I think I'll have to completely replace the dnd library to address. An intermediary solution may be to disable auto scrolling for larger payloads. |
Worked! Thank you so much @chrisvxd. |
Sometimes the website works fine, but at other times, it doesn't. I'm not sure why, but it occasionally occurs in production mode. |
When I hard reload my page and then go to the Puck Editor page, the issue occurs. |
This issue only occurred in production mode, dev mode worked correctly. |
@Sahak885 I'm unable to reproduce that in your reproduction repo. Since it's inconsistent, it sounds like it's a cache issue. Please try a different browser, reinstalling your next modules from scratch and deleting your |
I have done them, but the same issue exists in production after a hard reload page (CTRL + SHIFT + R). |
@Sahak885 can you reproduce in your https://github.com/Sahak885/puck-editor-frame-issue repo? I am unable to. |
I don't know why, but that issue occurred when using these two packages in the main repository
or
|
Thanks @Sahak885, I'll investigate further. |
@Sahak885 I could not reproduce your issues, but I have since published another canary that may help. Could you test with |
Puck Editor (version: 0.14.1)
Stack: Next JS pages router (version: 13.1.2)
Provide environment information
When I upgrade Puck Editor to 0.14.1, I encountered this error.
The text was updated successfully, but these errors were encountered: