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
In the kramdown specification I did exactly specify of what characters an ID name may be specified but didn't do the same for class names.
Keeping that in mind not allowing any character in class names would actually be a bug. However, the two characters I would not include are the dot and hash sign so as to make chaining class and ID names in attribute lists still possible.
Any thoughts on this?
And what do you mean by this:
(Note that I would require a space before the [^\s]+ language name; the more restricted current one maybe is useful when attached to the ~~~.)
This change modifies how kramdown handles class names that are defined
by using the special shortcut syntax in attribute lists or when adding a
language name to a fenced code block.
* When defining a language name for a fenced code block, any
non-whitespace character except the question mark is accepted. The
question mark separates the language name itself from URL-like
* In attribute lists a class name may be defined by using any
non-whitespace character except the dot and hash characters since
those are used for chaining together ID and class names without