Skip to content

fix(watermark): modify dom properties to regenerate #7149

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

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

jevin98
Copy link
Contributor

@jevin98 jevin98 commented Nov 30, 2023

Deeply monitor the changes in DOM tree properties of the entire watermark component

@jevin98
Copy link
Contributor Author

jevin98 commented Dec 1, 2023

@tangjinzhou This problem seriously affects the watermark component. Otherwise, users can easily modify the watermark DOM attributes using the console, causing the watermark to no longer display normally. Please merge it as soon as possible! Thanks!

@tangjinzhou tangjinzhou merged commit 0e6fd65 into vueComponent:main Dec 18, 2023
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy