Shane Caraveo (:mixedpuppy) Reporter
	Description • 10 years ago

Trying to use the remote-browser binding for the share panel (bug 1074553) simply causes a crash when opening the panel.

added the css binding:


browser[remote="true"] {
  -moz-binding: url("chrome://browser/content/tabbrowser.xml#tabbrowser-remote-browser");
}

And added remote=true to the share browser element.

building a debug version to get a trace...

	Shane Caraveo (:mixedpuppy) Reporter
	Comment 1 • 10 years ago

and here is a traceback on the crashing thread

	Shane Caraveo (:mixedpuppy) Reporter
	Comment 2 • 10 years ago

same stack trace when using this binding:

browser[remote="true"] {
  -moz-binding: url("chrome://global/content/bindings/remote-browser.xml#remote-browser");
}

	Bill McCloskey [inactive unless it's an emergency] (:billm)
	Comment 3 • 10 years ago

We have a fix for the crash in bug 1072980. However, the patch for that will just convert the crash to an exception. Is it necessary to make the frame remote, or are you just reporting the crash?

	Shane Caraveo (:mixedpuppy) Reporter
	Comment 4 • 10 years ago

(In reply to Bill McCloskey (:billm) from comment #3)
> We have a fix for the crash in bug 1072980. However, the patch for that will
> just convert the crash to an exception. Is it necessary to make the frame
> remote, or are you just reporting the crash?

- primarily reporting crash 
- otherwise investigating if I can use remote frames for the socialapi frames (and by extension things like loop and web panels).  so long as other interactions work correctly for non-remote frames (e.g. window.open), it's not a priority to make these remote.
- I'm fine with duping this to 1072980