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
Other specs tend to style notes in a way that calls attention with color while retaining adequate subtlety, yet we style them as if they were being consumed by encroaching fog blockquotes in GitHub Markdown.
WASM
HTML
CSS
ECMAScript
But notes are meant to be read—they may be "inessential" from the view of the spec as an implementation in itself, but they are often of key importance to the human reader, and I question whether we really mean to visually "background" them as such.
Solution(s)
I think we can do better, with a bit of Ecma orange! Here are a few possibilities.
1. Higher-impact approach
Specifically:
Make border full Ecma orange (like the metadata box), remove grey text color
Add background color which is Ecma orange with lightness bumped to 95%
(also make <code> background transparent and <td> background white)
Add 10px padding on the other three sides
Notes:
I say high-er impact because we could go further still and restyle the "NOTE" indicator if we wanted.
Since the border is full-colored, the background lightness here could even be bumped up further.
2. Medium-impact approach
Like the first approach, but without a border:
Remove grey border and its padding, remove grey text color
Add background color which is Ecma orange with lightness bumped to 95%
(also make <code> background transparent and <td> background white)
Add 10px padding on all sides
Notes:
This might be slightly less good for the printed version, where I believe background color would be omitted but border and padding would be preserved.
3. Lowest-impact approach
Basically the complement of the second approach:
Make border full Ecma orange (like the metadata box)...and that's it.
Notes:
I don't care for this since I really want to do something about the grey text color too, but if the note text is black-on-white just like the body text, I fear the border color alone isn't enough of a visual distinction.
Please note that I'm raising this discussion here, but the PR would need to take place in the ecmarkup repo, assuming we don't want it to be restricted to ECMA-262.
The text was updated successfully, but these errors were encountered:
Oh wow, I just realized that 402 is already using basically the exact style I've proposed here for a new element <emu-normative-optional> (which is not currently part of ecmarkup itself):
If Ecma orange is effectively doubling as a "warning" color there, then perhaps we should use green or blue as the color for notes instead?
Problem
Other specs tend to style notes in a way that calls attention with color while retaining adequate subtlety, yet we style them as if they were
being consumed by encroaching fogblockquotes in GitHub Markdown.WASM
HTML
CSS
ECMAScript
But notes are meant to be read—they may be "inessential" from the view of the spec as an implementation in itself, but they are often of key importance to the human reader, and I question whether we really mean to visually "background" them as such.
Solution(s)
I think we can do better, with a bit of Ecma orange! Here are a few possibilities.
1. Higher-impact approach
Specifically:
(also make
<code>
background transparent and<td>
background white)Notes:
2. Medium-impact approach
Like the first approach, but without a border:
(also make
<code>
background transparent and<td>
background white)Notes:
3. Lowest-impact approach
Basically the complement of the second approach:
Notes:
Please note that I'm raising this discussion here, but the PR would need to take place in the ecmarkup repo, assuming we don't want it to be restricted to ECMA-262.
The text was updated successfully, but these errors were encountered: