It seems there's no specific support for displaying long string actors.

This patch adds the .locked property for scopes and it also adds support for displaying long string actors.

Comment on attachment 704950 [details] [diff] [review] fix Review of attachment 704950 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/devtools/shared/VariablesView.jsm @@ +2001,5 @@ > if (!grip || typeof grip != "object") { > return true; > } > > + // For convenience, undefined, null nd long strings are considered primitives. Typo: and. @@ +2099,5 @@ > return "undefined"; > case "null": > return "null"; > + case "longString": > + return "\"" + aGrip.initial + "\""; Should we be adding an ellipsis here? Just wondering.

Thanks for the r+!

(In reply to Victor Porof [:vp] from comment #2) > Comment on attachment 704950 [details] [diff] [review] > fix > > Review of attachment 704950 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: browser/devtools/shared/VariablesView.jsm > @@ +2001,5 @@ > > if (!grip || typeof grip != "object") { > > return true; > > } > > > > + // For convenience, undefined, null nd long strings are considered primitives. > > Typo: and. Yep, saw this after I submitted the patch. > @@ +2099,5 @@ > > return "undefined"; > > case "null": > > return "null"; > > + case "longString": > > + return "\"" + aGrip.initial + "\""; > > Should we be adding an ellipsis here? Just wondering. I also thought this should be the case. I learned when I did the LSA work for the web console that, in practice, the method that gives you the string for the given actor grip should not include the ellipsis. You need to have special-casing in the code to add the ellipsis, to link it, to remove it, and so on.