On Tue, Sep 25, 2012 at 1:43 PM, Sebastian Zartner <[email protected]> wrote: > Ok. For that purpose it's better to use Break On Next as Honza described it. > Also note that there is a search field, which you can use to find > appearances of keywords like "submitSearchForm" in your code.
Great, thanks. > If you want to learn more about Firebug, you can also read other articles in > our wiki. > Yes, I am going through the wiki. I feel sorry for JS developers that had to do without Firebug at some time: it really is an indispensable tool for anything beyond the JS basics. >> >> > Sebastian >> > >> > PS: Using <button> tags for buttons offers more flexibility in designing >> > the >> > button contents (independently from the value that will be sent). >> > >> >> Thank you. I am just getting into Javascript development > > In this case it was a tip for HTML, not JavaScript. :-) > True, I shouldn't lump client-side technologies in the same basket as I mentally do. > There are several good tutorials, references and tips and tricks pages for > HTML, JavaScript and CSS. > Thank you very much. I have actually read some of those, especially the excellent W3Schools tutorials. It looks like I will need to purchase a "real book" PDF for advanced Javascript, though. I have no qualms about that. One thing that I do have qualms about is testing Javascript in other runtimes (browsers) without Firebug! I see that Chrome has some Firebug-clone debugging tools. -- Dotan Cohen http://gibberish.co.il http://what-is-what.com -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at https://groups.google.com/forum/#!forum/firebug
