On Nov 28, 4:36 pm, Jorge Alves <[email protected]> wrote: > Hi, > > I've noticed that using updatepanels in asp.net pages will render > Firebug's script tab useless. Instead of keeping the page source > updated it merely shows the resulting response of the updatepanel ajax > request. > > This makes debugging javascript in such pages really difficult, since > it messes with breakpoints, watches and everything else that still > lives in the rest of the DOM. > > How to reproduce (example): > > 1. go tohttp://demos.devexpress.com/aspxgridviewdemos/MSAjax/UpdatePanel.aspx > 2. make sure you have firebug's script tab loaded with the page source > (reload if needed) > 3. click one of the check boxes in the grid (this causes a ajax > request - partial postback in asp.net speak) > > Result: > The script tab only shows the response of the ajax request instead of > the whole page.
Yes, it looks like the URL for the Ajax response is the same as the page, so Firebug overwrites the source cache. If you use a different URL for the page or a different URL for the Ajax request I guess the problem will be avoided. jjb > > Tested with: > - FF4 b8pre (today's build) + Firebug 1.7X.0a7 > - FF3.6.14pre (today's build) + Firebug 1.6X.0b4 > > Thanks -- 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.
