We Keep Coding

Required props undefined in chrome 83

So after installing chrome 83 one of my pages in my app crashes. It says some of my props that's required is undefined. This only happens in chrome. I've tested in IE 11, Edge, Firefox and it works fine in those. It doesn't happen all the time either in chrome. Especially if i restart my localhost it might work a couple of times and then it starts breaking. I've also checked sha1d on master branch couple of weeks back and it also breaks there. This was never an issue before and started just recently. There has been no code changes for weeks related to that page. Any ideas what can cause this in chrome?

Based on what you are saying if problem only started happening recently in chrome, and this could be the failure of the prop-types library, its the library responsible for showing such a warning a required prop is undefined.
To make sure that it is indeed the problem of the prop-types library, you can switch environment to production, as this library should not work in prod. If indeed its the problem of this library you could try the following
Maybe try removing react dev tools and see if problem still happens
clean install of the library
update the library

batarang Chrome extension for AngularJS appears broken

(I added this post to a long series at Github of similar/recent experiences. I'm hoping someone here has an answer.)
Oh, good, I'm not just stoopid.
Trying to learn Angular on my own, from a book. When it calls out the use of batarang to show scope and models for a small sample script, and I fire up batarang, all I get is 'Scopes' over 'Scope()' on the left, and 'Models' over 'Select a scope to view its models.' and an 'Enable Inspector' button below that. Yes, I checked the box on the 'Enable' tab.
None of it seems to do anything.
On the 'Models' tab, clicking 'Scope()' (per the instructions on the 'Help' tab) does nothing, nor does clicking anything else. Weirdly, under the Options tab, I can check Show applications, Show bindings and Show scopes, These make pretty (and pretty useless) boxes around sections of the script's resulting page, above the dev tools pane, but all the checks clear as soon as I click another tab, like 'Models' (where nothing is working, still), and then come back to the Options tab.
Says I'm on "1.0.2 debilitating-awesomeness"...which is the AngularJS version, I suppose, but really describes batarang so far.
PS: I watched the video (http://blog.angularjs.org/2012/07/introducing-angularjs-batarang.html) but it was useless, as it assumes the thing is already working.
Oh, yea, Win7Pro64SvPk1, Chrome 34.0.1847.131 m 'is up to date'
Hope the other recommended tools work better, or at least work.
Meanwhile, can anyone confirm the status of batarang? Sure seems a lot of people have a dead extension.

Try "AngularJS Batarang (Stable)" by "spencer.leland". It works for me.
I use AngularJS 1.3.6 and Chrome Ver. 39

The last release of Batarang was over 10 months ago. It looks like it is no longer supported and does not work with Angular 1.2.x

I can confirm that the stable version (https://chrome.google.com/webstore/detail/angularjs-batarang-stable, version 0.4.3) works fine, with Angular 1.3.13 and the Ionic framework.
On the "batarang stable" page they even warn that this version works and the newer version doesn't.
I tried the newer version (https://chrome.google.com/webstore/detail/angularjs-batarang, 0.7.4) and it didn't work indeed, half of the options were gone from the UI.

I had issues with Batarang while running a page as a file with the file:/// protocol. Putting things inside Nginx and running the page from that webserver solved my problem.
This probably applies to Apache and any other web server. I am running Batarang 0.8.6 on Chrome Version 45.0.2454.85 (64-bit).
So, Batarang IS working in the latest version.

Windows Gadgets: Testing environment?

Is there anything that provides a console, error logging, etc. for testing Windows Gadgets? I've searched but I'm unable to find anything.
Thanks in advance!

A simple and easy start is to just use any web developing toolkit. I found out myself that for developing simple Windows Gadgets, Notepad++ and Firefox with its Web Developer toolbar was more than enough. You can implement all the business logic and just test the results in a browser. Actually starting it as a Gadget was only needed to fine-tune some graphical glitches that always occur because of different browsers still interpreting CSS a little differently.
Firefox has some nice tools for debugging Javascript.

You can use firebug lite for IE (i.e put a script tag and include the latest firebug lite version).It does look a bit crude but it works nonetheless and its seamless integration for testing.
http://getfirebug.com/lite/ie.html
Though your gadget might seem a bit mutilated when using it.
:)

Troubleshooting Help With IE8/Superfish Problem on SOME Computers Only

Our website uses the superfish jQuery plug-in for our menus (http://users.tpg.com.au/j_birch/plugins/superfish/), and they work fine in Firefox, IE6, IE7, Safari, Chrome, etc. ... and even in MOST IE8 installations. The problem is, in some IE8 installations, the menus don't work (they highlight on mouseover but don't drop-down the menu).
This has me baffled. In addition to a couple customer complaints, I've got one (Windows XP) machine in-house that reproduces the issue. However, I also have another Win XP/IE8 machine in-house which doesn't experience the problem. I'm used to dealing with JS/CSS issues between different browsers, but this issue between two machines on the exact same OS and browser is a bit much.
Oh, and just to further obfuscate the matter, the machine that is reproducing the issue shows no errors, Javascript or otherwise (even when I go in to developer mode). So ... does anyone have any suggestions on what could be going on?
As far as I know neither of my two "test" machines have any special plug-ins or anything which would cause the problem, they're identical in terms of everything that matters, and there's no JS error occurring that I can check the stacktrace of or anything. But this isn't just some crazy problem that's unique to my test machine, because as I said some customers have reported it too.
Any help would be appreciated.

Can you try setting the IE7 compatibility mode and see whether the problem persists?
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
(into the head of the document, best would be directly after <head>)
If it works then, you'll definitely know that it is some IE8 specific rendering issue. My first bet would be that your menu uses CSS hacks to set certain IE specific settings, unaware that IE 8 (fortunately) behaves differently and more standards-compatibly than its predecessors. If that is the case, you would have to use an IE8 specific CSS hack (or, better, specific style sheet) to "re-fix" those settings.
But first, check whether this really is the problem using the compatibility view.

Try turning off compatibility view: Tools -> Compatibility View -> Uncheck. I too struggled with this for the better part of an afternoon until I just tried this on a whim and it worked!

Try clearing Internet Explorers cache. Go to Tools -> Internet Options -> Browsing History section -> Delete ... -> Temporary Internet Files -> Delete.
For reasons unbeknownst to me, I've seen all IE versions start behaving strangely when the cache has been full or not cleared for a long time.

I have a Windows 7 64bit Home premium. The laptop encountered an issue called SupperFish.
First I tried resetting home page to different URL’s. IE8 kept returning to SuperFish.com.
Look in Add and remove programs, was not there, Not in startup or MSCONFIG (startup).
Third cleared Cookies then History. No help. Forth ran Microsoft Security Essentials, SpyBot S&D, Norton Constant Guard , Ad Aware. Problem is still there, Looked in C:\Program Files and found a folder called SuperFish, in that folder there was an Uninstall executable. I ran the Uninstall using a administrator account, and the problem is no longer showing up, after several hours of use.

not sure if it is a solution and that this is what you meant by not knowing how to fix it... but I cleared all my cache/history/cookies etc. from IE8 and if immediately worked (looking the same as other browsers).
maybe a fix for now but that worked...

This issue wound up going away without us ever figuring out what caused it, so now even if we did want to figure it out we can't (as we can't replicate). Therefore I can't really mark any of the above answers as correct, but since they exist I can't delete this issue either. So, I guess the best I can do is file this answer, but it's a rather unsatisfying one; sorry.

IE7 Crashing on some machines, errors in Debug bar, but don't see 'showstopper'

I've recently been made aware that my site is crashing in IE7. I tested it on a bunch of machines myself, but of course it always runs perfectly.
My brother just showed me IE7 on his computer, and it definitely crashes.
I've got 'debugbar' running, and it shows some errors in the HTMLCheck, and is warning that fb:login-button is not recognized (but of course it is allowed).
I run javascript check and it says
Script Error:
//----------------
Line: 1
Character: 6
Code: 0
Error Message: Syntax error
I can't actually see any script error myself.
The link is http://HearWhere.com
If somebody could help me figure out why this is failing on 15% or so of IE users, I'd be very very greatful.
Pete

Definitely does crash IE7 on a virtual machine I have. It's worth doing a bit of an audit for a start - for example, you're including and calling the Google Analytics JS twice, which is probably screwing up your stats if nothing else.
I've had crashes related to jQuery in IE7 before, all of which I could put down to large jQuery loops. Have a look through your code and comment parts where you are looping over the results of a jQuery select that could have a large number of results, or times when you are inserting a large number of elements into the DOM.

There's no Javascript errors (according to FireBug), but a large number of errors in the CSS for that page, any one of which could be antagonising IE7.

IE8 has a really nice javascript debugger, but it doesn't crash in IE8 for me. Previously I used Microsoft Script Editor for debuggin in IE 6 & 7. For some strange reason it's bundled with Microsoft Office! It's a bit hassle to setup, but it works.
http://www.jonathanboutelle.com/mt/archives/2006/01/howto_debug_jav.html

If you are crashing, the JS code is not a likely cause. You need to look at isolating the specific OS, IE version number, patch level, and external dependencies (versions of flash, etc).