You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since around 15-Dec-2016, the RDP inspector is broken - no packets are ever displayed in the UI and the addon logs an error about "window.postChromeMessage" being null.
Mozregression told me that the breaking change is bug 1322414. This changed the syntax for:
<browser type="content-primary">
to
<browser type="content" primary="true">
with no backward compatibility.
Fixing the <browser> elements in connections-window.xul and inspector-window.xul makes the RDP inspector work again.
A bad thing is that there is no way to specify content-primary in a way that works both before and after. But even if I remove the primary attribute, the inspector still works well, so maybe just <browser type="content"> is good enough in this case.
The text was updated successfully, but these errors were encountered:
jsnajdr
added a commit
to jsnajdr/rdp-inspector
that referenced
this issue
Jan 4, 2017
Since around 15-Dec-2016, the RDP inspector is broken - no packets are ever displayed in the UI and the addon logs an error about "window.postChromeMessage" being null.
Mozregression told me that the breaking change is bug 1322414. This changed the syntax for:
to
with no backward compatibility.
Fixing the
<browser>
elements inconnections-window.xul
andinspector-window.xul
makes the RDP inspector work again.A bad thing is that there is no way to specify
content-primary
in a way that works both before and after. But even if I remove theprimary
attribute, the inspector still works well, so maybe just<browser type="content">
is good enough in this case.The text was updated successfully, but these errors were encountered: