How Good C# Habits can Encourage Bad JavaScript Habits: Part 2 – False-y, Testing and Default Values, Comparisons, and Looping

This post continues to focus on areas where C# developers tend to make poor decisions when writing JavaScript based on their previous training. The languages are syntactically similar enough that C# developers tend to not invest the time to learn JavaScript’s differences.

The following post points out several misunderstandings that can get you into some confusing situations.

How Good C# Habits can Encourage Bad JavaScript Habits: Part 1

Many people come to jQuery and believe that their knowledge of a previous classical language (C#, Java, etc) will help them be successful at client-side scripting. You can use your classical language skills to accomplish a large amount of functionality with jQuery. However, the more client-side code you write you will find yourself uncovering strange bugs because you didn’t take adequate time to learn JavaScript properly.

jQuery tabs may be not work on Internet Explorer 10

There is a small problem for any developer that using jQuery UI tabs (tested on jQuery 1.8.2 and jQuery UI 1.9.2). Your website or exactly the jQuery tabs on you website may be not work. It create tab anchors (tab title) right, but nothing occur when user click it because the tab content panels do not load exactly by the way it should be.

The problem is the <base> html tag on your website. If you website using <base> tag example:

Display fullscreen website using javascript (Internet Explorer/Safari/Chrome/Firefox)

Until now, this is a great information, there are many browser that have implemented fullscreen supporting (Firefox, Chrome, Safari and must be a trick for Internet Explorer). That's so interesting for somebody want to do something with their website by make it fullscreen, may be great idea for webgame or something like that.