Bug 1911760 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
> I haven't been able to trigger this error. When do you see it?

It comes from Tor Browser. When a user is having trouble connecting to tor due to censorship, they can select their region to find them a suitable tor bridge. We basically do the following:

```js
const codes = Services.intl.getAvailableLocaleDisplayNames("region");
const names = Services.intl.getRegionDisplayNames(undefined, codes);
```

With ESR 128 we started getting the fluent message.
Revision 1 by
on 
> I haven't been able to trigger this error. When do you see it?

It comes from Tor Browser. When a user is having trouble connecting to tor due to censorship, they can select their region to find them a suitable tor bridge. We basically do the following:

```js
const codes = Services.intl.getAvailableLocaleDisplayNames("region");
const names = Services.intl.getRegionDisplayNames(undefined, codes);
```

With ESR 128 we started getting the fluent error message.

Back to Bug 1911760 Comment 5