Changes between Version 127 and Version 128 of DeveloperGuidelines/Tips


Ignore:
Timestamp:
12/03/13 07:50:49 (8 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Tips

    v127 v128  
    121121* http://code.google.com/p/web2pyorm/
    122122
    123 == CSS & Javascript debugging ==
    124 * use Firebug: http://code.google.com/support/bin/answer.py?answer=77412&topic=12044
     123== HTML, CSS, and Javascript debugging ==
     124
     125Each of the major browsers has tools available for viewing HTML page structure and form data, Javascript code, CSS.  Some also support Javascript debugging, including setting breakpoints and viewing values in variables.
     126
     127* Firefox: Install the [https://addons.mozilla.org/en-US/firefox/addon/firebug/ Firebug] plugin.  Start Firebug by clicking the bug icon in the upper right.  After the tools open in the lower half of the page, load the page you want to debug.
     128
     129* Chrome: Open the [https://developers.google.com/chrome-developer-tools/ Chrome developer tools] with Chrome menu (three bar icon) -> Tools -> Developer tools.
     130
     131* Internet Explorer: Open the [http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29 IE developer tools] with F12, or Tools (gear icon) -> F12 Developer Tools.  Note that you can test behavior of pages under earlier versions of IE by setting your current IE to behave as earlier versions.  In the developer tools menu bar, click Browser Mode and select the desired version.
     132
     133Other tools that may be of interest:
     134
    125135* use [http://www.sprymedia.co.uk/article/Visual+Event Visual Event] to see which events are active.
    126136* use Venkman: http://www.mozilla.org/projects/venkman/