diff --git a/index.bs b/index.bs index db579fb..8870f79 100644 --- a/index.bs +++ b/index.bs @@ -129,15 +129,15 @@ back to just logging the argument if it can't be parsed as tabular.

trace(...|data|)

-1. Let |trace| be some implementation-specific, potentially-interactive representation of the +1. Let |trace| be some implementation-defined, potentially-interactive representation of the callstack from where this function was called. 1. Optionally, let |formattedData| be the result of Formatter(|data|), and incorporate |formattedData| as a label for |trace|. 1. Perform Printer("trace", « |trace| »).

- The identifier of a function printed in a stack trace is implementation-dependant. It is also not - guaranteed to be the same identifier that would be seen in `new Error().stack`. + The identifier of a function printed in a stack trace is implementation-defined. It is also + not guaranteed to be the same identifier that would be seen in `new Error().stack`.

warn(...|data|)

@@ -183,11 +183,11 @@ Each {{console}} namespace object has an associated count map, which

Grouping functions

-A group is an implementation-specific, potentially-interactive view -for output produced by calls to Printer, with one further level of indentation -than its parent. Each {{console}} namespace object has an associated group stack, which -is a stack, initially empty. Only the last group in a group stack will host -output produced by calls to Printer. +A group is an implementation-defined, potentially-interactive +view for output produced by calls to Printer, with one further level of +indentation than its parent. Each {{console}} namespace object has an associated group +stack, which is a stack, initially empty. Only the last group in a group +stack will host output produced by calls to Printer.

group(...|data|)

@@ -235,7 +235,7 @@ Each {{console}} namespace object has an associated timer table, whic 1. Let |timerTable| be the associated timer table. 1. Let |startTime| be |timerTable|[|label|]. 1. Let |duration| be a string representing the difference between the current time and - |startTime|, in an implementation-defined format. + |startTime|, in an implementation-defined format.

"4650", "4650.69 ms", "5 seconds", and "00:05" are all reasonable ways of displaying a 4650.69 ms duration.

1. Let |concat| be the concatenation of |label|, U+003A (:), U+0020 SPACE, and |duration|. @@ -265,7 +265,7 @@ Each {{console}} namespace object has an associated timer table, whic 1. Let |startTime| be |timerTable|[|label|]. 1. [=map/Remove=] |timerTable|[|label|]. 1. Let |duration| be a string representing the difference between the current time and - |startTime|, in an implementation-defined format. + |startTime|, in an implementation-defined format. 1. Let |concat| be the concatenation of |label|, U+003A (:), U+0020 SPACE, and |duration|. 1. Perform Printer("timeEnd", « |concat| »). @@ -279,7 +279,7 @@ console when a given |label| does not exist in the associated timer table

Logger(|logLevel|, |args|)

The logger operation accepts a log level and a [=/list=] of other arguments. Its main output is the -implementation-defined side effect of printing the result to the console. This specification +implementation-defined side effect of printing the result to the console. This specification describes how it processes format specifiers while doing so. 1. If |args| is [=list/is empty|empty=], return. @@ -379,8 +379,8 @@ The following is an informative summary of the format specifiers processed by th

Printer(|logLevel|, |args|[, |options|])

-The printer operation is implementation-defined. It accepts a log level indicating severity, a List -of arguments to print, and an optional object of implementation-specific formatting options. +The printer operation is implementation-defined. It accepts a log level indicating severity, +a List of arguments to print, and an optional object of implementation-specific formatting options. Elements appearing in |args| will be one of the following: - JavaScript objects of any type. @@ -389,7 +389,7 @@ Elements appearing in |args| will be one of the following: optimally useful formatting applied. If the |options| object is passed, and is not undefined or null, implementations may use |options| -to apply implementation-specific formatting to the elements in |args|. +to apply implementation-defined formatting to the elements in |args|. How the implementation prints |args| is up to the implementation, but implementations should separate the objects by a space or something similar, as that has become a developer expectation. @@ -401,8 +401,8 @@ Printer should appear only within the last group on the appropriate gr group stack is not empty, or elsewhere in the console otherwise. If the console is not open when the printer operation is called, implementations should buffer -messages to show them in the future up to an implementation-chosen limit (typically on the order of -at least 100). +messages to show them in the future up to an implementation-defined limit (typically on the +order of at least 100).

Indicating |logLevel| severity

@@ -474,8 +474,9 @@ providing special behavior for each function, as in the following examples:

Printer user experience innovation

-Since Printer is implementation-defined, it is common to see UX innovations in -its implementations. The following is a non-exhaustive list of potential UX enhancements: +Since Printer is implementation-defined, it is common to see UX +innovations in its implementations. The following is a non-exhaustive list of potential UX +enhancements: