Tim Nguyen :ntim Reporter
	Description • 10 years ago

I was surprised that the add-on sdk didn't have access to this component. The editor component has a clear advantage over *just* CodeMirror.

So here's my proposal :

const {Editor} = require("sdk/devtools/editor");

let myEditor = new Editor(config);

// For manipulation, the methods are the same as the "internal" api

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

(In reply to Tim Nguyen [:ntim] from comment #0)
> I was surprised that the add-on sdk didn't have access to this component.
> The editor component has a clear advantage over *just* CodeMirror.
> 
> So here's my proposal :
> 
> const {Editor} = require("sdk/devtools/editor");
> 
> let myEditor = new Editor(config);
> 
> // For manipulation, the methods are the same as the "internal" api

This is a really good point, and I can see from your extensions that it would be really nice to be able to use a full-featured editor easily. 

+1!

	Erik Vold [:erikvold] (please needinfo? me)
	Comment 2 • 9 years ago

Are you referring to some code that is already shipped with devtools?

	Tim Nguyen :ntim Reporter
	Comment 3 • 9 years ago

(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #2)
> Are you referring to some code that is already shipped with devtools?

Yep, it's the code editor used in Firefox DevTools.

Code : http://mxr.mozilla.org/mozilla-central/source/browser/devtools/sourceeditor/editor.js

	Tim Nguyen :ntim Reporter
	Comment 4 • 8 years ago

Doesn't seem relevant with WebExt, so changing this bug's purpose.

	Brian Grinstead [:bgrins]
	Comment 5 • 8 years ago

There may be another bug about at least part of this, but I can't find it now.  Tom, do you know of anything?

	Tom Tromey :tromey
	Comment 6 • 8 years ago

(In reply to Brian Grinstead [:bgrins] from comment #5)
> There may be another bug about at least part of this, but I can't find it
> now.  Tom, do you know of anything?

Does "unprivileged" here means something other than the meaning used by devtools.html?
If it means "can run in content", then there are a few remaining chrome uses in sourceeditor.
One is being handled in bug 1289425.
I don't think we have a bug yet for the chrome:// uses in sourceditor, e.g.:
https://dxr.mozilla.org/mozilla-central/source/devtools/client/sourceeditor/autocomplete.js#12

If "unprivileged" here just means something about exposing this module to add-ons, then I don't
know of anything.