Skip to content

Conversation

@SisyphusZheng
Copy link
Contributor

@SisyphusZheng SisyphusZheng commented Apr 24, 2025

fix the ISSUE#2850 and ISSUE#2863 for input value leakage due to vnode reuse and Puppeteer screenshot functionality @marvinhagemeister if u have time plz check this change, thx!

SisyphusZheng and others added 3 commits April 24, 2025 05:35
…e when switching partials, which fixes input value leakage issues to slove the Open ISSUE #2850
fix the issue#2863,because the deno-puppeteer last updated is 3 year ago, and it is not suitable for deno2, we can use npm to slove the problem
@SisyphusZheng SisyphusZheng changed the title fix:Always generate a unique key for PartialComp to avoid vnode reus… Fix:fix the ISSUE#2850 and #2863 for input value leakage due to vnode reuse and Puppeteer screenshot functionality Apr 27, 2025
Copy link
Collaborator

@marvinhagemeister marvinhagemeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for opening a PR. Please split up this PR into multiple so that every PR does only one thing. This is crucial in open source to be able to do git bisect in the future in case something goes wrong.

To properly link issues in PR descriptions, leave out the issue prefix:

// wrong
ISSUE#1234

// correct
#1234

@SisyphusZheng SisyphusZheng changed the title Fix:fix the ISSUE#2850 and #2863 for input value leakage due to vnode reuse and Puppeteer screenshot functionality Fix #2850: Prevent input value leakage by generating unique keys for PartialComp Apr 27, 2025
@SisyphusZheng
Copy link
Contributor Author

THX FOR U ADVIES, I WILL REOPEN NEW PR TO FIX THAT,🙇

@SisyphusZheng
Copy link
Contributor Author

SisyphusZheng commented Apr 28, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants