On Monday, December 19, 2016 at 4:57:40 PM UTC+1, Arvis Pinkletter wrote: > > On Monday, 19 December 2016 02:36:18 UTC-5, Sebastian Zartner wrote: >> >> On Friday, December 16, 2016 at 4:17:41 PM UTC+1, Arvis Pinkletter wrote: >>> >>> The Debugger tab - in "sources", when I am working on a site where you >>> have to log in to see the page, I need the "source" of the page I'm working >>> on to be the same as the one in the browser, that is, if I'm logged into >>> the site, the source in the debugger tab for that page should also be the >>> "logged in" version of the page. Our pages redirect you to a login page if >>> you aren't logged in, so currently, in my "source" tab if I'm trying to >>> work on something, I see the markup and scripting for the login page >>> instead of the page I actually want. What's weird about this is that the >>> "inspector" tab has the right content, but not the debugger tab. >>> >> >> Do you have a URL, so this can be reproduced? Did Firebug (before Firefox >> 50) show different results? >> >> > Due to security reasons, I can't disclose a URL. But I can suggest this: > log in to gmail. You ought to be on a page with a URL that looks like > https://mail.google.com/mail/u/0/#inbox .... open up the Debugger, and > find mail/u/0/ in the sources. The source there ought to have links for > "sign in", "create an account", "get gmail", etc, while the browser's > viewport shows your inbox and not have those links. One thing I find weird > about this is that the "inspector" tab agrees with the viewport. > And yes, in firebug, when the script tab still worked, it showed sources > that matched the viewport. >
Hmm, I tested this with Firefox 49.0.2 and Firebug 2.0.18 right now and I couldn't find "create an account" or "get gmail" when I'm signed in. Though I think you are talking about dynamically evaluated scripts, i.e. JavaScript generated dynamically, e.g. via eval() or by inserting a <script> tag via appendChild(). There is a difference between Firebug and the DevTools in this regard. Firebug shows all dynamically evaluated scripts automatically while the Debugger in the DevTools only lists them when they have a <https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Debug_eval_sources>//# sourceURL <https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Debug_eval_sources> comment at the end <https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Debug_eval_sources> . Note that both tools show you the static source when you look at mail/u/0/ within the *Script*/*Debugger* panels, though the *HTML*/*Inspector* panels show a live view of the HTML. That means, changes to the DOM update the source shown in the HTML structure, though the source within the JavaScript debugger stays unchanged. Is it that what you mean? Also, scrolling up and down in the debugger tab isn't as nice as in the >>> inspector tab; I can't use my mouse pointer on the scroll bar - I have to >>> use my wheel or my keyboard to page up and down. >>> >> >> The Debugger panel is currently reworked >> <https://github.com/devtools-html/debugger.html> for a better UI and to >> be independent of the DevTools. You may try it out in the latest Developer >> Editions <https://aurora.mozilla.org/> and Nightlies >> <https://nightly.mozilla.org/> of Firefox. Try it out and let them know >> if it's still not working for you. >> > > OK, I grabbed the latest Developer Edition. Good news is that the sources > match the viewport. > Good! If I was wrong above, I'd still be interested in a simple reproducible test case to understand what you meant. > The vertical scrollbar on the source pane is *sometimes *clickable, if I > point my mouse on the exact perfect pixel, occasionally, but I can't find a > predictable way to make it always work. The vertical scrollbar in the > inspector works nicely when clicked, and I can drag the scroll-cursor up > and down at my leisure. > I saw that issue, too. I've filed it now as bug 1325604 <https://bugzilla.mozilla.org/show_bug.cgi?id=1325604>. Please add your notes if I missed something. On Friday, December 16, 2016 at 9:25:30 PM UTC+1, Arvis Pinkletter wrote: >>> >>> Console Tab: >>>> >>> XHR requests have "Headers", "POST", "Response", "Call Stack". >>> Need these that Firebug had: "JSON" (the nicely navigable JSON object >>> that is the Response), and "Cookies" >>> >> >> The JSON structure is available inside the *Response* tab. I'll add that >> to the migration guide >> <https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug>. >> > > Ah, I see. If I click the arrow next to my request, the response tab > there will show the JSON object tree after I click on "Size limit has been > reached. Click here to load more." I had thought it would just load the > rest of the Raw Data. > Right, the UI related to that is not that good yet. I think I've already filed a bug about that, though I can't find it at the moment. Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/045b77a9-680e-4707-b566-3c6abbce6813%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
