When a transition is skipped we need to explicitly handle any promise rejections or an exception is thrown. Does it makes sense to treat explicit skips separately from implicit skips (e.g. resulting from name collisions or attempting to start multiple view transitions on the same element/document)? Propose that if a developer explicitly calls skipTransition() on a view-transition then the promise rejections come as no surprise, whereas other cases could indicate an error in logic.

Discovered when adding WPT tests, when the test harness was complaining about the unhandled rejections unless suppressed with a setup option.