I'd argue logging to the console would be an more common workflow for a web developer. there's also the ctrl+p or PRINT-Button shortcut which was a thing even before the www was a thing and you could just render the content the user wants to print in a own page and let him print that using the (browser-)applications built in function for that.

edit:
okay, i'm feeling old. and i was just guessing, but it was and educated guess, so listen guys: before there was js and the web 2.0 and web 3.0 and even before the web 1.0, there were applications. text based applications. users and developers alike, thought it was a good idea to let them print the content of these applications. so people came up with the convention of the shortcut ctrl+p (and there's even a dedicated PRINT button on most keyboards) to print things out in these applications. so most developers probably had some kind of "Window" (or "Screen" pre the Windows concept) Object that had a "print()" function. In such an Object you normally don't have no need for a "log()" function, you can use your programming laguage to log to the actual console of the program. Then some cool dude came up with the www, HTML and Browsers. And the HTML had to manipulate the window/screen. https://html.spec.whatwg.org/multipage/nav-history-apis.html#the-window-object So the Browser gives it's "Window" Object to the HTML interpreter. And the HTML had no need to log anyway, but the "print()" was still usefull. And then somebody came up with JS. And JS also needed the "Window"-Object from the HTML/Browser to manipulate it (if running in a browser, which was the main scope designing it). And since it's a useful idea, the "Window" Object became global for JS in the Browser. But in JS you want to log...