If we had a complete testcase we could look into the issue. jjb On Mar 18, 12:50 pm, Sam <[email protected]> wrote: > hey thanks for responding. > > i find the article very interesting but my problem is not in the > scroll event, is on the resize one. > > i´ve been fiddling on this event every now and then and i have to say, > never had any problem before, even this bug would´ve never been > noticed if it wasn´t for the little distraction from my part of > deleting some js code and leaving a breakpoint in FB. > > here´s what happened: > > // Original code // > function somethingToDo(){ > bla bla bla bla > bla bla bla bla<---set a breakpoint here > > } > > $(window).resize(function() { > viewportY = $(window).height(); > viewportX = $(window).width(); > > }); > > //after deleting the function // > $(window).resize(function() { > viewportY = $(window).height(); > viewportX = $(window).width(); <-- breakpoint was here > > }); > > i didnt noticed the breakpoint was still on, i refreshed the page, and > the FB panel was blocking some content i needed to see so i dragged it > and it triggers the window.resize event (as long as the Firebug Panel > is attached to the browser window) > > thanks dude, nice article > > On Mar 18, 12:32 pm, Les <[email protected]> wrote: > > > > > > > > > See if this helps: > > >http://ejohn.org/blog/learning-from-twitter/ > > > Search for: > > > "It's a very, very, bad idea to attach handlers to the window scroll > > event"
-- 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 http://groups.google.com/group/firebug?hl=en.
