Public reach for WebSocketService agent appears to fail on Firefox

[kellytk]

Description

I'm submitting a ...

• bug report

A simple Yew app composed of a single app component and a single WebSocketService agent behaves incorrectly with Public and Global reach.

Expected Results

Agents with Public and Global reach should behave as they do with Context reach.

Actual Results

• Public doesn't initiate a WebSocket connection using Firefox, yet it does with limited success using Safari and Chrome.
• Global causes a panic in all three browsers.

I've made a simple example to demonstrate the behavior.

1. Clone/download and run cargo web start to serve it from localhost.
2. Modify the Reach value.
3. (Optional) Point it to a WebSocket server to verify the code functions correctly otherwise.

Context (Environment)

• Rust: v1.30.0-nightly (721913067 2018-08-26)

• yew: e6fc66e (latest master as of time of filing this issue)

• target: wasm32-unknown-unknown

• cargo-web: v0.6.15

• Latest versions of Firefox, Safari, and Chrome

• macOS

[hgzimmerman]

To narrow the scope of this issue, the Global reach shouldn't be investigated because it hasn't been implemented at all.

[samuelvanderwaal]

Missing label:

• bug

[jstarry]

@kellytk could you please check to see if you still see issues on Firefox for Public agents? Global agents aren't implemented yet as per #283