purbeast0
No Lifer
You can set breakpoints in your IDE for the UI when it's running in the browser?Mostly been doing .Net web apps, so just setting breakpoints, or adding robust error logging to provide debug info after the app has been deployed.
You can set breakpoints in your IDE for the UI when it's running in the browser?Mostly been doing .Net web apps, so just setting breakpoints, or adding robust error logging to provide debug info after the app has been deployed.
If it's logic in the code-behind, yes. I've only done it when debugging locally, allegedly you can do it by attaching to remote processes on the web server, but I haven't had the chance to get that running. If it's strictly front-end logic, no.You can set breakpoints in your IDE for the UI when it's running in the browser?
Yeah I'm not talking about debugging the backend. I'm talking about debugging the frontend in the browser. You can debug remote processes if you start the process with the right debug flags, so that it listens for the remote debug connection.If it's logic in the code-behind, yes. I've only done it when debugging locally, allegedly you can do it by attaching to remote processes on the web server, but I haven't had the chance to get that running. If it's strictly front-end logic, no.
Might be a question of target audience, maybe 10% of my work is front-end, and not aimed at consumers or for particularly wide consumption overall.Yeah I'm not talking about debugging the backend. I'm talking about debugging the frontend in the browser. You can debug remote processes if you start the process with the right debug flags, so that it listens for the remote debug connection.
It's mind boggling to me that people can be web developers and not use those tools, but I've worked with quite a few of them.
Even just the tools do modify css/html in the browser in Chrome are way better than FF.
Well when we're talking about browsers here which is the front end, which is why I brought up dev tools in browsers.Might be a question of target audience, maybe 10% of my work is front-end, and not aimed at consumers or for particularly wide consumption overall.
That's fine, I'm just saying I disagree with your assessment that Chrome is a superior browser 😀Well when we're talking about browsers here which is the front end, which is why I brought up dev tools in browsers.
If you're just doing backend work, then there isn't even any need for chrome or firefox. Just use a tool like postman to make requests and look at the data coming back.
Having worked with a number of them over the years, I'm more amazed than anything works 🙁
I regret to inform you that this is an urban legend that needs to be put to rest.I tell people it's like the Bumblee thing...they aren't supposed to be able to fly, according to what we know about science, and yet somehow, they do! 😀
I'm surprised to hear this too. I'm not even in webdev in any way and I use the chrome/edge dev tools fairly often to troubleshoot webpage issues (usually resulting in me opening a ticket with our webdev team). How is this not common?Yeah I'm not talking about debugging the backend. I'm talking about debugging the frontend in the browser. You can debug remote processes if you start the process with the right debug flags, so that it listens for the remote debug connection.
It's mind boggling to me that people can be web developers and not use those tools, but I've worked with quite a few of them.
Even just the tools do modify css/html in the browser in Chrome are way better than FF.
For home stuff, partly lazy, I don't browse the intertubes much outside of work. When I do, it's usually either on my mobile, which isn't really applicable to a pihole/external proxy of some kind, hence adblock/ghostery on FF mobile.Question: why are some of you fairly techy people using browser level ad blocking and not something like a pihole?
I think a lot of people simple don't use debuggers. Even on a new project I just started on, the other 2 devs on it had never hooked up the java backend to a debugger. That was like the first thing I did after I got the project up and running.I'm surprised to hear this too. I'm not even in webdev in any way and I use the chrome/edge dev tools fairly often to troubleshoot webpage issues (usually resulting in me opening a ticket with our webdev team). How is this not common?
I didn't have to do anything, once I re-launched Firefox, everything was back. I'm also on the current version, of course.On my Windows 7 platform I cannot even perform the so called fix. I'm running 52.8.0 32-bix FF ESR and the described instructions does apply to versions this old. But the bug sure does affect versions this old.
I didn't have to do anything, once I re-launched Firefox, everything was back. I'm also on the current version, of course.
Question: why are some of you fairly techy people using browser level ad blocking and not something like a pihole?
