Quote:
To see whether to see if the if statement is a problem and confirmed that it was the problem
trying random changes to see what is going on is not a solution. The only way to go is to display
e and check if contain is as expected.
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
JavaScript Debugging[
^]
Chrome DevTools | Web | Google Developers[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.