Debug

Delivering a proper and rich experience to every browser and device combination boils down to best practices. Nearly any browser and device combination will properly render error free and concise code. If you have taken the extra step to add browser specific code and or added fall back code, you should be set.

Being that the real world is what it is, let’s assume you have an error in one specific browser and or device. Go back to basics.

  1. Validate all code used on that page, to ensure there are no errors
  2. Check for “non-error mistakes” (calling a Class Vs. an ID)
  3. Boil the effect or action down to the core of what you are trying to do, and see if it is supported where you are having the error
  4. Check to see if you included the code needed for that device and browser combination to read and render the desired effect or action
  5. Make sure the effect or action you called achieves the effect or action you think it does
  6. Eliminate possible conflicts (don’t load CSS or JavaScript that may be conflicting)
  7. Isolate the effect or action in a sandbox or a blank page
  8. Ask for help. Experts are great, fresh eyes are nearly as good

Still can’t get that error to go away? Did you …

  1. Make sure you did not fail to close something – “}” “;” ETC
  2. Do something drastic to clear the cache
  3. Make sure you are editing the correct file, line, rule (add “TEST” or change the color)
  4. Change the name of the rule or file
  5. Close everything and open it back up, and start over
  6. Set it down for an hour

Can I Use

Remember! The browser and device combination is rendering exactly what you told it to, nothing more and nothing less.