update to reflect the fact that console has spec #1382
Conversation
As `console.*` functions are supposed to follow the spec https://console.spec.whatwg.org/, the text about it is updated.
|
"supposed to follow the spec" is a bit of a stretch. This spec is not even complete, very early draft, and not even in conformance yet with all browsers. Maybe a few years from now it'll be the official standard, but certainly not yet. |
|
@getify I agree that the spec is actually in its early stage. But "There is no specification" is not entirely true, right? Would you be okay with changing just that part? |
|
It was entirely true at the time of writing. It's partially true still. It's worth potentially re-visiting in second edition, but I'm not convinced that we'll be at a point where that spec is having any influence on the browsers' behavior. Right now, they mostly do whatever they want, in service of developers. Having worked on a devtools team before, I can say that browsers tend to treat those tools as a way to differentiate from other browsers in the effort to attract developer mindshare. So I find it at least somewhat suspect that we'll ever be at a place where the console is entirely consistent according to a spec. Right now, the spec's only stated goal is to document that which the consoles already do (mostly I would guess so that other implementations can more easily adhere if they want to). It's not even complete at that, yet. But until the major browsers indicate strongly they plan to adhere to it, and importantly, to adhere to each others' standards, I'm not sure how close in spirit to a "spec" this document will ever be. Always remember: specs are opt-in by implementations. A spec is only as good as participants choose to adhere to it. |
getify
force-pushed
the
master
branch
6 times, most recently
from
5cb284a
to
8af48e2
Compare
As
console.*functions are supposed to follow the spechttps://console.spec.whatwg.org/, the text about it is
updated.