WHATWG on 2023-09-08

05:32	<annevk>	Or maybe it would be cleaner if we made `Observable` a special type in Web IDL, so you wouldn't be able to return async iterables, but had to instead return an Observable or Stream, which I think is what we would (always?) want.
08:59	<Domenic>	Yeah I came around to that conclusion actually
09:00	<Domenic>	Well or something like it
09:00	<Domenic>	https://github.com/domfarolino/observable/pull/60#issuecomment-1710883833
22:02	<Alexander Kalenik>	I am working on implementing navigation, and I'm struggling to determine if the specification explicitly defines that the population of history entries initiated for nested navigables should be aborted after parent navigable navigates to another page. For example, the following scenario currently fails with an assertion: Both the nested navigable and the parent navigable navigate to a new URL. The population of SHE for the parent navigable finishes first. "finalize a cross-document navigation" for the parent navigable replaces the SHE (assuming historyHandling is set to "replace"). The population of SHE for the nested navigable navigation concludes. "finalize a cross-document navigation" for nested navigable fails to locate the SHE to be replaced (assuming historyHandling is "replace") because it was located in the nested history of the parent navigable SHE that was replaced earlier. Does that sound like a specification bug or I am missing something?