to be honest, I don't want to lose my 60 tabs.
On Monday, January 14, 2013 5:14:48 AM UTC-8, Sebastian Zartner wrote: > > I do not see any errors scrolling your script using FF 18.0 + FB 1.11.1 on > Win7. > My steps: > > 1. Opened Firebug on http://jesusnjim.com/common/js-stringtodtime.html > 2. Enabled and switched to the *Script* panel > 3. Reloaded the page > 4. Chose *time-funcs.js* from the Script Location Menu > 5. Scrolled up and down using the mouse wheel, the scrollbar and the Page > Up/Down keys > > So please install Firebug into a fresh Firefox profile and try it again. > If you still see these problems, please provide clear steps how to > reproduce them. > > Sebastian > On Monday, January 14, 2013 9:40:24 AM UTC+1, Jim Michaels wrote: >> >> ...and sometimes the program counter/pointer disappears, I think when I >> alt-tab to my editor to look at something. >> >> On Sunday, January 13, 2013 11:45:46 PM UTC-8, Jim Michaels wrote: >>> >>> scrolling down in a .js file is very hard. jumps and flickers a lot on >>> my really old and slow pentium 4 HT 2.8GHz (1 core 2 threads) on firefox >>> 18.0. >>> >>> also, there is another problem where sometimes if the code syntax is bad >>> js won't execute it and the debugger won't kick out an error either. js and >>> debugger just give up. it just sits there (both browser and debugger). >>> browser is scrollable though, unlike during debugging sessions (which I >>> suppose can be expected since scroll events are probably DOM and js events). >>> not sure about this condition. maybe js cuts itself off from the world >>> if the syntax is bad enough "I throw up my hands" type of thing? :-) >>> some of my function calls were missing newly added arguments, etc. >>> >>> >>> -- 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
