You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently no callers in the spec sets the force bypass cache flag as pointed. I just left it there for some potential use from implementers (e.g. calls from devtools) as of now.
There's another aspect. Algorithms in other specs are supposed to dispatch their functional events by invoking Handle Functional Event which calls Soft Update at its last step without setting the flag. I'm not sure whether it makes sense but some algorithms may want to call Soft Update directly and with the flag set on their own need.
Does the above usage make sense? Or should we drop the flag?
Currently the SoftUpdate algorithm takes a "force bypass cache flag". How does this ever get set? Is it needed any more?
The text was updated successfully, but these errors were encountered: