Bug 34351 – Webinspector features arranged

• Status: RESOLVED
• Resolution: INVALID
• Component: Web Inspector (Deprecated)

[Rodrigo Romero]

for all we work, ebkit is not a browser but a framework, and since it is used for more than just a browser, there are some features missing in the development of this framework, small features mostly added inside a browser (as a plugin or extension) for developers to work on webapps or websites, but the fact is that since you are working in an application from the main framework there are a set of features missing that if added to the end point could open access to the application cycles making it slow, so controlling the access but having the information there to be used by any additional extension is a better approach.

This is why, taking all the features inside web inspector we find there are some features missing there that could help in the framework development process and also to the ended applications using it.

PART ONE
Web Inspector RESOURCES Section Features Request (Performance):
Optimizing caching — keeping your application's data and logic off the network altogether
Minimizing round-trip times — reducing the number of serial request-response cycles
Minimizing request size — reducing upload size
Minimizing payload size — reducing the size of responses, downloads, and cached pages
Optimizing browser rendering — improving the browser's layout of a page

How to do it?

Resolving DNS names
Setting up TCP connections
Transmitting HTTP requests
Downloading resources
Fetching resources from cache
Parsing and executing scripts
Rendering objects on the page

PART TWO
Web Inspector ELEMENTS Section Features Request (Inspection and Correction):
Ability to edit, debug, and monitor HTML, CSS and JavaScript live
Visualize CSS metrics
CSS Layout with box model shading

NOTE: Most of the features are part of two projects called PageSpeed (PART ONE) and Firebug (PART TWO), but these features call is not to use their code or a part of it at all, but to use the Best Practices in Rendering and execution (for PART ONE) and for error debug and correction (for PART TWO) as to so webinspector can make use of this information for development. But the fact is that these two projects are the most used out there for web development do most likely features will coincide because they are following what the developers community is asking for development as we should do too.