Masked input

[Nymoth]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• [X ] ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

• I have linked an issue or discussion.
• It's submitted to the main branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• I have updated the documentation accordingly.
• All tests are passing
• New/updated tests are included
• I have updated the "upcoming" section inside docs/changelog.md explaining the changes I contributed

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[colinscz]

Hi @Nymoth
thanks for the contribution, please reach out in the teams webcomponents channel in case you have any questions or approach somebody of the core team.

[pennal]

Hi @Nymoth,

first of all, thank you for your contribution!

We have discussed this PR internally and have decided not to merge it. The reason is that we believe this functionality is better done at the framework level, instead of the webcomponents level. This way the users can decide the library that fits their use case best, depending on the frontend framework (or lack thereof) being used