mathiasbynens / mathiasbynens/caniunicode

Section on whitespace?

Open
#1 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
35
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Is it worth adding a section on whitespace?

One example that comes to mind is the infamous U+180E (https://github.com/mathiasbynens/regexpu-core/commit/9b10d2a597d4e56b236cae0f9aa2f21a9c6d1122), which used to be an ECMAScript whitespace character but no longer is one since ES2015.

I’m leaning towards this not being worth it, since the definition of whitespace is relatively stable at this point (both in ECMAScript and in Unicode).

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named. Review the repository's existing feature sections and the cited Unicode and ECMAScript whitespace definitions before deciding whether this topic belongs; done means documenting the decision or adding a clearly scoped whitespace section.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.