–
Aman

I have not heard reports of page inspector not opening at all.

I’m happy to hear that the crashing problem you had encountered is fixed!

Yes, the Chrome incognito mode is nicely done, and I am certain there have been discussions around that for Firefox. I personally use multiple profiles (a bit hard to get going initially… launch Firefox from the command line with -ProfileManager), because then I can have different Firefoxes running at the same time but not conflicting with one another.

That’s a different part of Firefox and I don’t know how the priorities shake out there. I do know that some form of that feature is under consideration.

Thank you for the wonderful product.

PS – A reason I use GC is it allows me to have the incognito window and normal window open simultaneously. Helps when I want to login as different users into my applications. This happens more than you would expect. A feature like that would be greatly appreciated as well.

1. we are definitely still making UI improvements here, including the ability to put the controls in a separate window. keep an eye out here for future release announcements

2. the “Properties” view is alphabetized. The “Rules” view is in specificity order.

3. You should close the page inspector before interacting with the page. The page inspector binds a bunch of keys to make them useful while navigating elements for inspection.

4. layout view is in the works!

5. there are pluses and minuses there, but generally I agree with you and we are looking at options

6. same for this. we are currently deciding how we want to approach the equivalent of a “network panel”

7. javascript debugger is in the works (the first bit of code just landed on Tuesday)

Also, I’ll note that the 3D view was created as a Google Summer of Code project last summer and then simplified and polished for inclusion in Firefox. If we didn’t already have the code, we would have certainly been working on other features ahead of that one. Sometimes things make it into the product at unpredictable times (especially in open source!)

wrt server push – FF does not yet accept server push – we are waiting for the flow control mechanisms of spdy/3 (or better) to be defined before using it. Partially for the concerns you describe.

re CPU – crypto is absolutely required. We won’t make that mistake again. And SPDY is much more CPU friendly than HTTP/1 over SSL because it terminates so many fewer connections (and the RSA operation of the connection termination is the major cost of SSL – not the bulk cipher on the stream).

As for compression, its used in a very targetted way with very small windows (which matter for both RAM and CPU)- a lot of thought has gone into this. Your whole stream is not just passed through gzip. The value is extraordinary.

wrt small hosters: we need to do a better job of running the PKI. But the emphasis should be on making sure users are running secure protocols as the first order of business. users first.

i m recently working on the same issue. does anyone know, if our lovely internet explorer will have something similiar?

if you press “F11″ even internet explorer switches to fullscreen modus like every other browser. unfortunately you cannot fire a F11-keypress event via javascript due security reasons.

I think “Server push” may be a nice advertising feature for SPDY-inventor google, but a really dangerous hole because theroetically a bad server can push any bad content or unsolicited ads to the browser without using client-side scripts.

As a second drawback, there is no CPU saving, because servers and clients need to decrypt AND decompress and client-side CPU usage may be a real problem in mobile devices.

The third problem are SSL certificates. Small hosters won’t and in some case even can’t install SSL-certificates, mostly because hosters are afraid of the additional CPU usage for SSL-encryption in shared environments.

My advice is to use SPDY:// instead of HTTP://. The user can choose his benefits by choosing the protocol.

2. It would be nice to have the CSS properties listed in an alphabetical order under the “Rules” section (they seem arranged randomly right now).

3. The inspector seems to be very greedy and does not relinquish control. Every time I hit “return” in this textarea with the Inspector present even if minimized to the narrow bar, it toggled the “Inspect” feature instead of entering a new line as I wanted it too.
Note – I could use the alphanumeric keys with the inspector turned on but not the “arrow keys” or the “return” key which was very misleading!

4. Definitely need a layout inspector to view actual element dimensions.

5. Every time I inspected an entry under the any section in the “Web console” it opened a new window leading to a huge collection of pop up windows left to be closed!

6. The “Net” section in the “Web console” needs to be much detailed than its present state. GC style separate Net section or FireBug style inline section would be much preferred than the popup style.

7. JavaScript inspector and debugger are also very desirable.

I am positive you must have recognized these needs and are already working towards a better product but a 3D look before a JS inspector just doesn’t inspire confidence.

Lastly, I would like to offer my thanks for providing us with a cool product and look forward to seeing it improved and possibly eliminate the need for external developer tools.

Thanks,
Aman