Trying out: - `#f2f2f4` for the default message border in light theme; somewhere in between Grey 10 (`#f9f9fa`) and Grey 20 (`#ededf0`). Grey 10 is very hard to distinguish from white on most screens (especially as a 1px line), so an intermediate value seemed to made sense. For comparison: Chrome uses `#f0f0f0`. - No border between command and output, when not separated by a log result. We still keep a border when there is a log between command and output (e.g. if the command is `console.log(something)`). We keep borders if the result is an Error. Checked in Chrome, and this is what they do too.
Bug 1519904 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Trying out: - `#f2f2f4` for the default message border in light theme; somewhere in between Grey 10 (`#f9f9fa`) and Grey 20 (`#ededf0`). Grey 10 is very hard to distinguish from white on most screens (especially as a 1px line), so an intermediate value seemed to made sense. For comparison: Chrome uses `#f0f0f0`. - No border between command and output, when not separated by a log result. We still keep a border when there is a log between command and output (e.g. if the command is `console.log(something)`). We keep borders if the result is an Error. Checked in Chrome, and this is what they do too. Another question: do we want to keep the 3px blue border shown on the left when hovering a row? With borders, it might become less useful?