Morten Nielsen

@azchohfi Here's what I did to get around it: Just added an attribute that automatically gets picked instead, since the namespace match the unit tests: https://github.com/dotMorten/XamlBehaviorsWpf/blob/b289e419a832f64e4e4277715cb7eb75e2c41721/Test/UnitTests/STATestMethodAttribute.cs

@azchohfi Ugh that's a lot of changes. I'd suggest considering my approach as you don't have to touch any of the test code, so it's easier to maintain in the...

At what point are you calling this method? Does it still happen if you delay the call?

There's only one state parameter. The second one you see is encoded as part of the first one. This happens because the webauthenticator uses the state parameter to resume the...

> why with the name state if it already exists? Because it's part of the oauth standard to use `state` as a parameter for roundtripping back to the redirect. Most...

btw your string is encoded incorrectly: `&state=provider=1`. Shouldn't that second `=` be encoded?

> yes, but why we do we have to set 'state' twice? > `state=appInstanceId%3d6e4168e9-a66a-4258-aae4-2921d57804ff%26signinId%3d9a25feea-f024-4430-8528-75cef7132cdd%26state%3dprovider%253d1` Again the state isn't set twice. It is set once, and there happen be the string...

It does look like the oauth playground service has changed and is no longer correctly preserving encoding of the state parameter. This is a service issue, and not a WinUIEx...

> I tried to downgrade WinUIEx from 1.5.0 to 1.7.0 and 1.6.0 and it didn't change. Are you saying if you downgrade to 1.5.0 though, the problem goes away, indicating...

Can you share some user stories why this is needed? I’m not really following why you’d limit the maximum resize on your users.