116 plus ones
Shared publicly•View activity
View 5 previous comments
- Jul 11, 2012
- I am still using Firebug as dev tool - if Chrome don't start to show full ajax request info in console I suppose I will not use it as main dev tool at all (It is very annoying because Chrome is the best browser but it is lacking such an important feature)Jul 11, 2012
- Hi Todor – what information would you like to see in the console?
Take a look at Chrome Canary for an idea of what's already been implemented: Canary displays the URL of the file retrieved, which links to detailed information in the Network panel. In the console, you also get a link to the function that makes the Ajax request. You can also add XHR breakpoints: go to XHR Breakpoints from the Scripts panel (Sources panel in Canary).
If none of that is what you want, let us know – or file a bug at new.crbug.com.Jul 12, 2012
- Hi Sam and thanks for the comment.
Yes I know that Chrome dev tool has all the things (and even more) that Firefox has but in Chrome they are not so "close at hand". For example - I have to debug several ajax requests (more than one time) - in Firebug I have all the information about them in my console and I don't have to go anywhere else. In Chrome:
1. First I have to enable XMLHttpRequests (which should be enabled by default - correct me if I am wrong but I don't know a web site in our time which is not using ajax).
2. When I click the dropdown arrow I see information that I do not understand and is not useful for me.
3. When I click the link I am redirected to the network panel where I see a lot of requests and I am lost and not knowing which one to choose.
4. When I finally find it and click it the panel changes (which is also unpleasant because I have to go several panels back to where I was) and I see some unformatted information which costs me additional energy and frustration to read.
I know that Google is working really hard on Chrome and you are doing great by pushing Html5 forward but the natural and easy way of working with the new technologies is also important. I don't know about you but I just cannot stand to debug for example 10 ajax requests following the above steps.
I am writing this hoping that things will change for good. I also hope that some of your colleagues from the Chrome team will hear this.
(I will also post this as a new issue on the Chromium site's link that you gave me).
Todor PavlovJul 12, 2012
- Thank you for your feedback! And yes, you should definitely file a bug at crbug.com/new where we would be able to discuss issue in greater detail!
I think I now understand your workflow. You are testing your backend using the DevTools and you are issuing commands in the console that fire XHRs against your server. When you type a command, you expect to see XHR entry in the console as a feedback to your action. Is that right? I think we don't do particularly good with this scenario. Let me try to explain why we have it this way.
> 1. First I have to enable XMLHttpRequests (which should be enabled by default - correct me if I am wrong but I don't know a web site in our time which is not using ajax).
> 2. When I click the dropdown arrow I see information that I do not understand and is not useful for me.
> 3. When I click the link I am redirected to the network panel where I see a lot of requests and I am lost and not knowing which one to choose.
This sounds bad. We should open that particular XHR for you. Please file a bug.
> 4. When I finally find it and click it the panel changes (which is also unpleasant because I have to go several panels back to where I was) and I see some unformatted information which costs me additional energy and frustration to read.
As I mentioned above, we don't seem to handle "XHR debugging using console" scenario well. Please get back to us with the issue filed and we'll make sure it gets fixed.
PavelJul 13, 2012
- Hi Pavel,
Thank you that you took the time to explain me your point of view for this problem. I understand you but still there should be an easy way to test XHR.
I posted a bug on crbug.com and I will post a separate one about that clicking a XHR link leads to the Network panel and not to the XHR itself.
TodorJul 13, 2012