export some definitions for css-navigation-1 #12003
Description
What is the issue with the HTML Standard?
The css-navigation-1 spec draft currently has a bunch of definitions that link in to non-exported definitions within the HTML spec. I'd like to figure out how to avoid doing this, which will probably involve the HTML spec exporting some additional definitions. (css-navigation-1 is still in a somewhat early stage, but I think the feature set is likely close enough to what we want to think there's a reasonable chance that the set of concepts it needs to be exported from HTML might be close to correct at this point).
At this point I have encapsulated the problematic definitions all in their own section within the spec, § 4. Definitions of current navigation state, which contains 4 definitions ("current from url", "current to url", "current navigation type", and "current navigation delta") that examine state about the currently-active navigation, which are referenced by other parts of the spec.
Some of these definitions also have some open questions (the most significant being whether it makes more sense to look at the ongoing navigate event or the transition when examining navigation state when the "old" page is still the active document).
I don't think it necessarily makes sense to expose this exact set of definitions from HTML -- HTML could certainly expose things that css-navigation-1 could build its definitions on top of -- but in the current state I don't think css-navigation-1 can do this without using non-exported definitions.
While I'm happy to make a PR for this at some point, I though it was (maybe?) better to start off the discussion with an issue rather than going straight to a PR.
cc @noamr