The `name` reactive property at https://lit.dev/playground has unexpected and possibly unintended behavior
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
The playground linked from lit.dev is (I think) trying to demonstrate a reactive property. However, changing this property doesn't actually do anything because of the `name` attribute set in the html.
I'm not sure if this was intentional to demonstrate this interaction, but it made for a slightly wonky onboarding experience where I thought things were broken
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening the playground linked from lit.dev and reproducing the behavior described in the issue, then inspect the HTML containing the name attribute and the reactive name property. Confirm the intended interaction and adjust the playground so changing the reactive property has an understandable visible effect without unexpected interference from the HTML attribute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100