finger pointing

[Cantor, Scott]

On 5/10/21, 2:41 PM, "users on behalf of Paul B. Henson" <users-bounces at shibboleth.net on behalf of henson at cpp.edu> wrote:

>    Why is that? I'm not that familiar with the view mechanism, but why would it be any different than the saving
> storage view that gets called, displays stuff, and then moves on to the next one? Or does that use a trick like
> you refer to but in a scenario where you have to?

We use Javascript in most of the cases where we have to automatically do something because the feature usually already depends on it.

We use meta refreshes, I just think it's a hack. It's all hacks, and I don't like introducing hacks when it's not critically necessary.

>    Hmm. Would I be able to detect in the interceptor whether or not the request was going to complete with a
> redirect?

You'd be using a meta refresh anyway so if the next step is a view, it's not going to matter and if the next step is a redirect it should be the thing that's left on the screen.

> Or would I need to use this mechanism for both the redirect and post scenarios rather than add content to the
> post view?

You'd have to do both.

> Wouldn't this mechanism also require a meta-refresh or other JavaScript automation in order to load
> "$flowExecutionUrl&_eventId_proceed=1" to proceed without any user interaction?

Yes, but one is you doing what you feel is necessary and one is asking us to bake it into the code for everybody.

-- Scott