Norm Radder wrote:Question: How do you debug CSS and javascript to find errors and/or correct behavior?
In Firefox, the F12 key opens up its diagnostic console. You can use its network tab to make sure that all of the secondary URLs (css, javascript files, images) are being fetched. Obviously, if parts are missing, the client cannot do its job properly!
Once that's done, you can confirm what CSS options are in effect for page elements using the Inspect CSS option. You can also edit the CSS (including adding/removing style elements) to tweak appearance, then use what you've learned to make permanent changes to your application source.
JavaScript is supported via an interactive debugger. You can set breakpoints, single-step, the usual stuff. The only caveat is that if you're using a complex third-party JS library, the stock distro form basically compacts it all into a single very long ugly line. Most such libraries have an alternate URL that returns the script in unpacked form as well so that you'll have discrete lines to select for breakpoints (not to mention readability!)
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
