925046 - Add 'suggestions' tool giving tips for improving page's performance, accessibility, code structure etc.

Status: RESOLVED DUPLICATE of bug 1415357

Description

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

I find the Chrome devtools advice about how to structure code helpful.  Our devtools could give advice (summarized across all tabs) that might help improve the "Firefox as Web IDE" story.

Comment 1

[Sebastian Zartner [:sebo]]

(In reply to Gregg Lind (User Advocacy - Heartbeat - Test Pilot) from comment #0)
> I find the Chrome devtools advice about how to structure code helpful.

Where can this advice be found? And what info does it contain exactly?

Sebastian

Comment 2

[Sebastian Zartner [:sebo]]

Gregg, I still couldn't find the feature you mentioned. And I am wondering how this 'suggestions' tool should work.

Sebastian

Comment 3

[Sebastian Zartner [:sebo]]

As I didn't get any feedback so far and the feature description is very vague, I close this bug now.

Note that MDN is planning to integrate more into the DevTools, which is somewhat related, I guess. But again, I never saw this "advice about how to structure code" within the Chrome DevTools, so I'm unsure what it does exactly.

Sebastian

Comment 4

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

Created attachment 8752264 [details]
Screen Shot 2016-05-13 at 11.54.30 AM.png

Screenshot showing CHROME DEVTOOLS AUDITS pane, with advice for developers about specific page issues.

Comment 5

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

Sorry for the late answer.  See attached screen shot.  Under dev tools > audits, it suggests things are likely (for some opinion of likely) to be problem areas.  Even if the answers are cargo cult-ish, it gives the illusion of 'something to do', and user benefit.

Comment 6

[Sebastian Zartner [:sebo]]

Ah, now I see what you mean. It's something like YSlow[1] and Page Speed[2] for Firebug.
This is indeed something very desirable. The Firebug Working Group previously discussed to implement something like this in upcoming Firebug versions. Therefore I'm CC'ing Honza.

I could imagine this tool to include even more features than only performance analysis. It could also provide accessibility advices (like FireEyes[3] and AInspector) and tips for tightening up your code (like CSS Usage[5]).

Sebastian

[1] https://getfirebug.com/wiki/index.php/Firebug_Extensions#YSlow
[2] https://getfirebug.com/wiki/index.php/Firebug_Extensions#Page_Speed
[3] https://getfirebug.com/wiki/index.php/Firebug_Extensions#FireEyes
[4] https://addons.mozilla.org/de/firefox/addon/accessibility-inspector-for/
[5] https://getfirebug.com/wiki/index.php/Firebug_Extensions#CSS_Usage

Comment 7

[Sebastian Zartner [:sebo]]

Regarding accessibility, I saw right now there is already a very nice and very well integrated extension for the DevTools called aXe Developer Tools:

https://addons.mozilla.org/firefox/addon/axe-devtools/

Sebastian

Comment 8

[Sebastian Zartner [:sebo]]

Bug 1415357 was recently filed by the DevTools team covering the same feature and acting like a meta-issue. In the hope that that bug gets more traction, I mark this one as a duplicate of it.

Sebastian