Skip to content
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: use Shadow DOM to avoid CSS conflicts #13

Merged
merged 1 commit into from
Oct 15, 2024
Merged

fix: use Shadow DOM to avoid CSS conflicts #13

merged 1 commit into from
Oct 15, 2024

Conversation

motea927
Copy link
Owner

πŸ”— Linked issue

#12

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

To avoid global Tailwind CSS preflight and class name conflicts, this PR isolates the plugin's styles by utilizing Shadow DOM, ensuring that plugin styles do not interfere with the project's global styles.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly (for new feature).

@motea927 motea927 merged commit b0de5c6 into main Oct 15, 2024
4 checks passed
@motea927 motea927 deleted the dev branch October 15, 2024 11:57
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.

1 participant