Bryan Clark (DevTools PM) [:clarkbw] Reporter
	Description • 7 years ago

Lets remove the Shader Editor from DevTools.  

I do think this use case is important and we need to continue to support the ability for tools like this to be created, however I don't think that currently we're adequately addressing the needs of this use case and more importantly we are shipping a bad product.

This tool is fairly broken, does not (nor planned to) support WebGL2, sees very little usage, and is not actively maintained.

We are able to get intermittent errors like the following when running on basic WebGL pages:

TypeError: replayContext[name] is undefined
Stack trace:
replayAnimationFrame@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/canvas.js:598:9
generateScreenshotFor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/canvas.js:79:22
handler@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/protocol.js:1082:19
onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1769:15
receiveMessage@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:761:7

There 32 open bugs https://bugzilla.mozilla.org/buglist.cgi?component=Developer%20Tools%3A%20WebGL%20Shader%20Editor&product=Firefox&bug_status=__open__&list_id=13457985 plus others (like bug 939602) which are reported incorrectly.  

The triage owner no longer works on DevTools and we don't have anyone else who can take over.

Over a 90 day period Telemetry reports 1800 opens on release, 25 on beta, 125 on aurora, and 8 on nightly; those are just opens, not usage numbers but they are incredibly low. Only the web audio editor is opened less than the shader, but the web audio editor is still working fairly well.

A possible second life for the editor could be on GitHub where people interested in it could work together to improve and maintain it as an extension. The code is already available to those who want it and will continue to live in the source code record.

	Jeff Griffiths (:canuckistani) (:⚡︎)
	Comment 1 • 7 years ago

One thing that would be interesting to think about for this issue is the usage relative to other tools. If there are 1800 open events on release, how does that number compare to the other more popular panels?

	Bryan Clark (DevTools PM) [:clarkbw] Reporter
	Comment 2 • 7 years ago

Yes, sorry that's a good question.  In the same period of time (on release) we see these numbers for other popular panels.

Inspector       Console         Debugger        Network
4,553,729	3,435,693	1,030,222	572,219

So 1800 opens is very very low.

	Tim Nguyen :ntim
	Comment 3 • 7 years ago

(In reply to Bryan Clark (DevTools PM) [:clarkbw] from comment #2)
> Yes, sorry that's a good question.  In the same period of time (on release)
> we see these numbers for other popular panels.
> 
> Inspector       Console         Debugger        Network
> 4,553,729	3,435,693	1,030,222	572,219
> 
> So 1800 opens is very very low.

Part of why the Shader Editor is less used than the 4 other tools is that it's disabled by default, and a lot of people don't know about it.

	Jeff Griffiths (:canuckistani) (:⚡︎)
	Comment 4 • 7 years ago

The webgl shader editor tool for chrome has 4800 users[1] despite very good reviews. I think there is a relatively small group of developers who are interested in I've editing shader programs in browser devtools - in chrome or Firefox. Offering this functionality in an extension might actually improve its discoverability, but I think only to a point.

[1] https://chrome.google.com/webstore/detail/shader-editor/ggeaidddejpbakgafapihjbgdlbbbpob?hl=en

	Bryan Clark (DevTools PM) [:clarkbw] Reporter
	Comment 5 • 7 years ago

(In reply to Tim Nguyen :ntim from comment #3)
> Part of why the Shader Editor is less used than the 4 other tools is that
> it's disabled by default, and a lot of people don't know about it.

That's part of it. But the storage editor is 12,039 opens (12x the shader) and it is also off by default so it doesn't explain all of it.  Its more of a niche panel.

	Yulia Startsev [:yulia] Assignee
	Comment 8 • 5 years ago

Depends on D14732

	Masatoshi Kimura [:emk]
	Comment 10 • 5 years ago

What is the replacement of this feature? WebGL Inspector for Firefox is no longer available.

	Yulia Startsev [:yulia] Assignee
	Comment 11 • 5 years ago

:emk - There are a few alternatives in the form of web extensions, we are looking into how best to communicate this to users of the panel, through a popup or similar. The panels will not disappear immediately -- these patches are to show an initial look at what the removal might be like. Here are the mentioned extensions. 

- Shader Editor Extension (https://github.com/spite/ShaderEditorExtension)
- Spector.js (https://addons.mozilla.org/en-US/firefox/addon/spector-js/#&gid=1&pid=2) 

A bit about why this is happening: This panel has been unmaintained for a lot time and is currently blocking other significant efforts in DevTools. We considered migrating this to a web extension, but after looking at the usage (less than 0.02% of users open the panel, while development on these panels for DevTools wide updates takes up to 20% of developer time) and getting feedback from the community, it became clear that the amount of time it would take to migrate it would not make sense as it would take time away from other resource critical areas. It is unfortunate, but the team is stretched quite thin at the moment. 

You can find more detail in this thread: https://groups.google.com/forum/#!topic/mozilla.dev.developer-tools/bYUl2b5qXUE

	Masatoshi Kimura [:emk]
	Comment 12 • 5 years ago

Will you accept any new patches to Shader Editor? I'm asking because I was writing some patches recently. (bug 1340912 and bug 1340914) If not, I'll withdraw patches and close these bugs.

	Panos Astithas (he/him) [:past] (please ni?)
	Comment 13 • 5 years ago

Although we do appreciate your patch contributions, unfortunately at this point in time it doesn't make much sense to accept them when we're in the process of removing the panel. Thank you for the effort!

	Yulia Startsev [:yulia] Assignee
	Comment 14 • 5 years ago

Thanks for jumping in Panos,

Yes, unfortunately we won't be able to accept those patches. Thank you for the effort, we will be closing bugs related to these panels shortly.

	Pulsebot
	Comment 15 • 5 years ago

Pushed by nbeleuzu@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f75b89bf0aa4
remove Shader Editor Panel; r=vporof
https://hg.mozilla.org/integration/mozilla-inbound/rev/06a583daf142
remove Shader Editor Actor and Front; r=vporof
https://hg.mozilla.org/integration/mozilla-inbound/rev/75b49fcc2743
Backed out 13 changesets (bug 1342237, bug 1403944, bug 1403938, bug 1528296) for subsuite gpu failures CLOSED TREE

	Pulsebot
	Comment 16 • 5 years ago

Pushed by ystartsev@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7e2abdd135b8
remove Shader Editor Panel; r=vporof
https://hg.mozilla.org/integration/autoland/rev/be2c8c170852
remove Shader Editor Actor and Front; r=vporof