Reject multiple IDs

At a glance

The post suggests that the ability to add duplicate IDs could be mimicked in the token system, where users can only add a token name once. The community members discuss the purpose of unique IDs, with one member acknowledging that while unique IDs are best practice, they personally find it useful to be able to target multiple elements with the same ID. Another community member agrees that using duplicate IDs is not the best practice, but notes that implementing a system to prevent it could be challenging for the development team.

Useful resources

JJeremy

Within the property settings, you can add IDs that are the same wherever you like.

With your token system, you can only add the token name once. Could that be mimicked on the ID section so a user couldn't duplicate them?

4 comments

AAlex

Hey Jeremy, thanks for the suggestion 🔥!

Tokens are like this because they are tied to other things (like styles), as to ID's aren't.

But maybe I'm misunderstanding the goal here.

Why do you want to prevent a user from duplicating IDs?

JJeremy

Simply because the IDs should be unique. 🙂

The first sentence in the Mozilla docs. https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/id

AAlex

Thanks J.

I understand why to have them be unique (especially for anchor links) though I personally also find it useful to be able to add multiple instances of the same ID. Sometimes I like to target multiple elements in my scripts by ID and just use the same over over and over.

Though might not be best practice. 🤷

I'm sure the product team will have more insights on this when they start their day.

JJeremy

haha yep, not the best practice. But at least you own it. 😉

I could see this being somewhat of a pain to implement for the dev team.

Add a reply

Join the Webstudio community

Reject multiple IDs