liveview-native / liveview-native/liveview-native-core
Attribute priority: first wins
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 166
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Accoridng to the HTML spec when it comes to duplicate attributes the first defined attribute is the one that wins. Subsequent attributes of the same name are ignored:
I just want to confirm that we are adhering to this as well in the SwiftUI client.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Inspect the SwiftUI client’s handling of duplicate attributes and compare it with the HTML first-wins rule; done means confirming that behavior or documenting a reproducible discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100