Six Common Mistakes DotNet Guys Always Does

I have been working with DotNet team from last 2 years. I am responsible for all UI (User Interface) related problems. I have been noticed that my team mates always stuck on the same kind of issues while handling UI. These are very common HTML, CSS and Browser related issues of everyday exercise.

I feel that DotNet guys don't give such importance to UI part as they give to their controls and functions part. They always keep UI part bottom in their priority list. At last when application going to launch they stuck in UI related issues. Now the solution is just review following mistakes at initial stage:

1. HTML Tags

One and only most common mistake is HTML Tags. I agree that application code is very lengthy but forget to closing (</tag>) a tag is big mistake. So keep close HTML Tag at the end of your code. If you have used so many tables in a page then try to handle all tables through CSS.

2. Table vs Div

Now the second most common issue is Tables and Divs. Make sure what to use either Table or Div. It always create big problem at time of browser compatibility. So, don't mix-up Table code with Div.

Example:

<table>
<tr>
<td><div></div></td>
<td></td>
</tr>
</table>


Using a tabular data in a table is correct but using a non-tabular data in table is semantically wrong.

3. Understand CSS units of measurement

I have been noticed some times while fixing UI related issues that DotNet guys never care about units of measurements. Some times they use px (pixel), % (percentage), em, and pt altogether which is not correct. My advice is to review CSS properly before start.

Read more about CSS units of measurement

4. Non-Standard GUI Controls

Basic GUI widgets like command links and buttons, radio buttons and check-boxes, scrollbars, close boxes, and so on — are the lexical units that form dialog designs vocabulary. Changing the appearance or behavior of these units will confuse readers.

5. Nested Tables

Nested tables always cause a problem when you are using a so many tables in page. It is very difficult for a UI design to fix nested tables at time of browser compatibility. Use CSS for good HTML.

6. Violating Design Conventions

One thing should keep in mind that don't lose consistency because consistency is one of the most powerful usability principles: when things always behave the same, users don't have to worry about what will happen. Instead, they know what will happen based on earlier experience.

Do you have any suggestions? Leave your comment.

Related Posts :