I have always relied on the Firebug console tab within Firefox to display complete ajax calls, my systems all use ajax extensively and its useful to be able to monitor the calls in one listing. Ive always found Firebug to be the most complete version of this, and it is this one feature that has prevented me from migrating to any other browser including FFs own developer console, where the only way to determine the endpoints is to hover over the request, or spend two mouse clicks on opening up the response panel followed by the "Params" tab. Neither of these are very useful in a working environment.
In the latest FF however, I find that Firebug is deprecated in favour of the built in developer console, so I figure that if Firebug is to disappear, there must be a way to configure the replacement to my liking.
Heres an example output side by side, the right hand side (Firebug) displays not only the endpoint but all parameters right in the line, for example "ajax.php?home&act=counters", whereas the left hand side (built in console) simply displays "ajax.php" for all calls.
The URL parameters are displayed for requests logged to the console since Firefox 60.
In case the URL isn't shown completely (due to the width of the window being too small), the URL is cropped, though you can still see the complete URL when hovering the request.
Furthermore, the URL parameters are also displayed within the Network Monitor.
Related
This seems to be by design as far as I can tell. Selenium can see the initially loaded HTML, but not the HTML after it's been massaged. I've tried IE, Chrome and PhantomJS and they all show the same behavior. So does the built-in Chrome debugger, until you inspect an element on the page, you can't query any of the rendered HTML.
I'm looking for any suggestions about how to scrape the web page. The only option I see right now is finding the chrome process, triggering the inspector, clicking inside, then running the Javascript. Needless to say, this sounds fragile.
I also haven't been able to find anything on capturing the Ajax calls from selenium so I can make them and capture the JSON. When tried copy / paste from the chrome network tab into selenium I got a missing application block message.
Does anyone have any other advice?
Since I can replicate the issue in the chrome debugger, I don't see posting code as useful. It looks like a design decision.
Ralph
Sadly, I wasn't able to do things in a straightforward way. Instead, I used Selenium to do the login and navigate to the page, then use windows API calls to click inside the window send ^a^c to copy the data and an absolute location to click on the button to go to the next page.
The site is set up so that ^a^c copies the raw data for this site. I don't know if that's standard for Angular or not.
Fragile, but it works.
I am running the latest version of Chrome on Mac Lion. I added a FB like button to my page which works fine on Firefox but does not work on Chrome for some reason. There seems to be a quick window pop-up which tries to load and then it disappears without the "Like" taking place.
Fiddle - http://jsfiddle.net/luisp128/X7SDR/3/
I thought it might be related to this prior question, but FB said this issue was already resolved: the the popup window ("flyout") of a like button doesn't show up in a chrome extension
One thing to note is that you must be logged into Facebook within each browser for the FB buttons to appear in that browser (otherwise the buttons have no context). If not, the buttons are not shown.
So, if you're seeing this problem, open a new tab, log into FB, and then refresh the original tab - the buttons will then appear (assuming there isn't a second problem)>
I have manually implemented the Flattr button to my site.
In Firefox (Windows) the "popout" covers the button so one can't press it.
Any other browser renders the popout in the correct place. Can someone confirm this? Or is it a conflict on my site?
Since you don't mention which site is yours I'm left to speculate on the reasons for this and if I do then I think it is that your body-element doesn't start at the top left of your browser and that therefor positioning of the popout fails due to browsers inability to correctly account for offset body elements.
We've had reports of people experiencing this problem in eg. WordPress where the admin-bar that's showed when a user is logged in pushes the entire site down 20 pixels or something and makes the position of the popout be of by 20 pixels. Could it be something similar for you - that you're logged in in Firefox and not in other browsers?
As far as I know there's no workaround for this limitation - eg. jQuery can't account for it either.
Good thing though: If your layout has a body with an offset or something else that makes the popout not work for you you can disable it by setting popout 0 in the settings of the button.
Is there any way to see AJAX requests like in FireBug for Firefox? I am interested in what was posted and the response/html returned.
I tried developer tools' profiling and debugging. I didn't see any place where it shows this stuff.
Press F-12, click NETWORK tab.
I just removed IceWeasel from my Debian machine and replaced it with Firefox so I could test the website I'm developing in the more popular browser in case there was any minute differences and I noticed that google's keyboard navigation no longer works. I've done some searching (the hard way, with the mouse :P) and I can't find any mention of a link between Debian or firefox and problems with google keyboard navigation.
When I press the up and down keys, the whole window just scrolls. Also when I press the tab key, firefox just moves from link to link (starting with the google tools links in the top left-hand corner) and takes 10 - 15 tabs before it gets to the search results.
I read somewhere that google instant wasn't available in all countries (or, at least it wasn't some time in the past.) I use google Australia, but I've also tried - via an international proxy server - google.com and I still get the same results.
I also like to have images disabled for general browsing due to strict bandwidth allocations and I thought perhaps the feature was working, but not displaying the blue arrow indicator. However, when I enabled images for google.com and google.com.au, there was no observer change in behaviour (except for the images showing up.)
Has anyone else experienced this problem, either using firefox, or under any other conditions?
The broken keyboard navigation I'm encountering type ahead find. Particularly, typing, optionally beginning with '/', is directed to the search box, regardless of the document element with focus.
There are two ways to fix this:
Use the general.useragent.override pref to remove "Firefox/XXX" from the user agent string.
Use a userscript (Greasemonkey) to reclaim keyboard navigation (theoretical)