820395 - Need localizable errors for RTCPeerConnection

Status: NEW

(Core :: WebRTC, defect, P4)

Description

[Randell Jesup [:jesup] (needinfo me)]

Per smaug's request in bug 812886.  However, doing "jsfind 'throw new Error'", I see hundreds of non-localized strings, and no localized ones.  So do we need to do this?

From PeerConnection.js:

  throw new Error("Can't create RTPPeerConnections when the network is down");
      throw new Error("Constructor already called");
      throw new Error("PeerConnection not enabled (did you set the pref?)");
      throw new Error("createOffer already called");
      throw new Error("createOffer passed invalid constraints");
      throw new Error("createAnswer already called");
      throw new Error("setRemoteDescription not called");
      throw new Error("No outstanding offer");
      throw new Error("createAnswer passed invalid constraints");
      throw new Error("setLocalDescription already called");
        throw new Error(
          "Invalid type " + desc.type + " provided to setLocalDescription"
        );
      throw new Error("setRemoteDescription already called");
        throw new Error(
          "Invalid type " + desc.type + " provided to setRemoteDescription"
        );
      throw new Error("Both maxRetransmitTime and maxRetransmitNum cannot be provided");

Comment 1

[Axel Hecht [:Pike]]

What happens with those errors?

Comment 2

[Adam Roach [:abr]]

(In reply to Axel Hecht [:Pike] from comment #1)
> What happens with those errors?

These are only used by software developers to troubleshoot programming errors. They are not the kind of thing we have historically localized; see Bug 827843, comment 6.

Comment 3

[Bulk Bug Changes for mreavy's org]

Mass change P3->P4 to align with new Mozilla triage process.