- -
>> (Now, who invented a keyboard where
>> “,” and “.” are adjacent as well as “;” and “:”?)
>
> I'm sure you realize this, but I'm just saying it for the
> sake of other readers:
>
> In CSS, the semicolon does /not/ terminate a declaration,
> it /separates/ declarations within a ruleset.
>
> ruleset : selector? '{' S* declaration? [ ';' S* declaration? ]* '}' S*;
>
> Therefore, if a ruleset has just a single declaration,
> no semicolon is required.
Yes, I see your point about the redundancy of semicolons in the case given.
Yet, I’m used to ending CSS declarations (as well as statements in some
programming languages that have similar rules) with a semicolon, just
for simplicity and for being prepared to adding a new declaration (or
statament or whatever).
But it seems that I’m getting too old for that. And my (rather off-topic
and rhetoric) question was about keyboard design. Why make similar
characters like “.” and “,” adjacent? Regarding “:” and “;”, the US (and
UK) keyboards are more sensible than Finnish keyboards (where they are
in adjacent keys, with Shift), given the rather different uses but
similar appearance, both in (human) languages and computer codes such as
HTML and CSS. Why would you make it easier to people in err in things
like that, so that slight mistyping results in characters that look too
similar but are quite different in meaning?