You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While not exactly relevant, the why for capitalization is probably a carryover from early times of computing before even ARPANET was a thing; Decades ago when everything was text-based and terminals had a varying levels of features (colors, charsets, row length, bandwidth etc.) one of the neatest tricks to detect feature compatibility automatically was to check username capitalization during login. Computers started as caps only, lowercase came later, so having an user submit their username as lowercase meant a more modern baseline of features for the terminal connection.
Spec does not mention that lowercase should be ok, rather, to me it reads as if it should not be allowed: https://spec.commonmark.org/0.29/#cdata-section.
The “Block” version of commonmarkjs behaves correctly and does not allow lowercase, but because of the single regex to parse “inline” html, it’s allowed.
Input:
Yields:
Expected:
The text was updated successfully, but these errors were encountered: