docs: explain the attribute model — data-numkey is the switch, the rest are options#2
Merged
Merged
Conversation
…st are options Readers couldn't tell data-numkey and data-numkey-locale apart: the README listed the attributes in one flat table without saying that data-numkey is what binds an input (and that every other data-numkey-* attribute is inert without it), and the locale option had no examples showing default vs auto vs pinned-tag behavior. - README en/ko: 'How the attributes work' section with an on/off/anti-example block, table now marks data-numkey as THE switch, new 'Locale-aware display' section with the three variants and per-browser outcomes, plus the form-POST caveat (display value is what posts — getValue before submit) - demo site: same three-variant snippet in the locale card
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why / 왜
data-numkey와data-numkey-locale의 차이가 문서에서 드러나지 않았습니다 — 속성들이 평평한 테이블 하나에 나열돼 있어서,data-numkey가 바인딩 스위치이고 나머지data-numkey-*는 그것 없이는 아무것도 하지 않는 옵션이라는 구조가 안 보였고, locale 옵션은 default/auto/고정 태그의 동작 차이 예제가 없었습니다.Readers couldn't tell the two apart: the flat attribute table never said
data-numkeyis the on-switch and everything else is inert without it, and the locale option had no default-vs-auto-vs-pinned examples.What / 무엇
<input data-numkey-locale="auto">단독은 ✗ 아무것도 안 함), 테이블에서data-numkey를 스위치로 명시getValue)Verification / 검증
Docs + demo HTML only, no runtime change. typecheck ✓ · 49 tests ✓