Navigating reserved clients

[jakearchibald]

What happens if .navigate() is called on a reserved client (from resultingClientId)?

Failing in this case seems like the simplest thing to do. In this case the developer could navigate the replacesClientId.

[jakearchibald]

Alternatively, if .navigate() is called on a reserved client, we could try and redirect that call to the associated client that would be replaced.

This association doesn't exist right now, but it may be developer-friendly to create it.

[wanderview]

I think we decided that it should reject over here? #1034 (comment)

I guess the F2F note does not mention the navigate() method itself, just the properties.

[jakearchibald]

I thought we discussed it, but couldn't find the comment. I'll leave this open so we confirm at the f2f, but yeah I think rejecting is the right choice.

[wanderview]

Yea, I'd much rather expose the target client ID and let script redirect to their request there themselves instead of trying to do some kind of auto-magical mapping cross-process.

[jungkees]

Misclicked.

I agree to reject on reserved client.

[jakearchibald]

#1216 could remove this problem

[jungkees]

#1216 could remove this problem

And #1034, #1035.

[jakearchibald]

Makes it sounds like a good idea 😄

[jakearchibald]

We aren't going to expose reserved clients, so this is no longer an issue.