Live data from Hacker News

Web developer tool secrets that shouldn’t be secrets

christianheilmann.com

101–108 of 108 posts

Re: Web developer tool secrets that shouldn’t be secrets

#101
post #54

Earlier quoted context omitted.

I live in Missouri, in the deep Red Ozark Mountains in the SW part of it and I shared an article on that on FB in a local group. Our Governor really blew it on this one. Folks here will generally stand by their GOP Party and for the most part they never talk about Parson here but this really pissed them off. I was surprised by the comments and the number of them. They are pissed about the incompetence of those who bu…

FYI the P in GOP already stands for Party.

lol... yeah that was a typo. I make those sometimes to see if anyone will notice.

Re: Web developer tool secrets that shouldn’t be secrets

#102

Earlier quoted context omitted.

For what it’s worth, reading the ECMAScript spec was one of the best things I’ve done to deepen my work as a developer. It doesn’t touch on console commands, but these do: https://developer.chrome.com/docs/devtools/console/api/ https://developer.mozilla.org/en-US/docs/Web/API/console https://nodejs.org/api/console.html It’s not that I’m just reading language docs all day, but I’ve found it to be a really productive u…

Thanks. However, that's 4 separate links that you've provided. (R)ead (T)he (F) antastic (M)anual suggests there is one to be referenced. It's not read a manual. That's kind of the point. When it comes to programming, there is no single manual. You learn some basics, roll up your sleeves, and bang out code. You get to something you're unfamiliar, so you look it up. You learn something new. You go back to bang out cod…

> However, that's 4 separate links that you've provided. (R)ead (T)he (F)antastic (M)anual suggests there is one to be referenced. It's not read a manual.

That’s not what RTFM means and has never meant that. The definition is an angsty way to tell the inquirer to stop bothering whomever and go look it up. The number of sources is irrelevant.

If you’re going to go so far as to change Fuck to Fantastic, then Manual can be changed to Manuals.

Re: Web developer tool secrets that shouldn’t be secrets

#103

"Overrides allow you to store local copies of remote scripts and override them when the page loads. This is great if you have, for example, a slow build process for your whole application and you want to try something out. It is also a great tool to replace annoying scripts from third party web sites without having to use a browser extension." Overrides are useful not just for "developers". Why is this option hidden…

Ctrl-Shift-P brings the command palette up without the ">".

Re: Web developer tool secrets that shouldn’t be secrets

#104

Earlier quoted context omitted.

console is not part of the language, iirc it was first introduced by Firebug - or some similar debugging tool then every other environment implemented something with the same syntax for their environment but slightly differing behaviors since not a part of the standard (of course you can also find things in a standard that vary by implementation, but things that are not in the standard I distrust even more)

I see, thank you.

so I guess the correct spec (based on browsers / Node following it) is https://console.spec.whatwg.org/

on edit: https://github.com/whatwg/console

Re: Web developer tool secrets that shouldn’t be secrets

#105

Earlier quoted context omitted.

As far as my understanding goes (which may not be very far at all), the common base seems to be Chromium. When I want to debug an HTML source (like the one in the article), VSCodium offers me Chrome or Edge as the base browser (none of which I have installed). I wonder why Brave isn't in there, since it's also Chromium-based.

Oh, I think I understand now. You mean when you use the debugger in Visual Studio Code the target browser dropdown only shows Edge or Chrome and not Brave? That is weird and I wonder if it has something to do that brave hasn't got the CDP methods turned on that allows other software to remotely control it. In essence, the debugger spawns a new instance of the browser and controls it remotely from VS Code, much like a…

Yes, that's what I meant. And thank you for the explanation.

Re: Web developer tool secrets that shouldn’t be secrets

#106
post #44

This is more of a "hacker" tip than something for web developers but "Show Page Source" will show you the full raw HTML for any page. Be careful where you use it though as it is illegal in some states.

Very annoyingly it doesn't show you the full HTML for the page you're viewing. It does a new HTTP request (I think without cookies at least in Firefox) and shows that. This means you need to use inspect element if you have dynamically generated HTML either from JS or non-idempotent server sides.

Re: Web developer tool secrets that shouldn’t be secrets

#108
post #44

This is more of a "hacker" tip than something for web developers but "Show Page Source" will show you the full raw HTML for any page. Be careful where you use it though as it is illegal in some states.

Very annoyingly it doesn't show you the full HTML for the page you're viewing. It does a new HTTP request (I think without cookies at least in Firefox) and shows that. This means you need to use inspect element if you have dynamically generated HTML either from JS or non-idempotent server sides.

Annoyingly most browsers do this. One of the first things we implemented in Orion browser was to use the source you already have.
Post reply on HN