Add support for Navigation API

[suryarajendhran]

Currently the navigation object is not available in the DOM and while the Navigation API is still experimental there is decent support for it in modern versions of browser. It'd be great to have it available as part of the default typescript DOM types.

[HolgerJeromin]

decent support for it in modern versions of browser

Not, sadly it has not, according to MDN database

https://github.com/microsoft/TypeScript-DOM-lib-generator#why-is-my-fancy-api-still-not-available-here

A feature needs to be supported by two or more major browser engines to be included here, to make sure there is a good consensus among vendors: Gecko (Firefox), Blink (Chrome/Edge), and WebKit (Safari).

https://developer.mozilla.org/en-US/docs/Web/API/Navigation_API#browser_compatibility
Blink only

[rogerpadilla]

We can reconsider this, it is 75% close now.

[mathe42]

It is still Blink only.

A feature needs to be supported by two or more major browser engines to be included here, to make sure there is a good consensus among vendors: Gecko (Firefox), Blink (Chrome/Edge), and WebKit (Safari).

https://developer.mozilla.org/en-US/docs/Web/API/Navigation_API#browser_compatibility

[justinfagnani]

Even though the Navigation API is currently only shipping in Blink, it has consensus support and is landed in the HTML spec, and seems nearly ready in WebKit.

• Navigation API in the HTML Spec
• WebKit standards position: support
• Webkit implementation PRs
• Mozilla standards position: positive
• Mozilla implementation issue

[HolgerJeromin]

If another browser is ready to ship it will be added (by a hard-working volunteer) to browser compatibility data and automatically added to this repo via a bot.
No need to send updates to this issue tracker before this is done...

[fregante]

While this is discussed here, anyone landing on this issue can install this package:

npm install --save @types/dom-navigation

https://www.npmjs.com/package/@types/dom-navigation