<p dir="auto">Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.</p>
<p dir="auto">There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="543332647" data-permission-text="Title is private" data-url="https://github.com/denoland/deno/issues/3557" data-hovercard-type="issue" data-hovercard-url="/denoland/deno/issues/3557/hovercard" href="https://github.com/denoland/deno/issues/3557">#3557</a>). All that knowledge should be written down and presented to end users to avoid multiple questions/bug reports about purposeful incompatibilities and/or missing implementations.</p>
<p dir="auto">I'm not sure if this is intentional, but much of the deno doc output is missing when using the default output format (not json).</p>
<p dir="auto">For example, only the names of interfaces are displayed and not their functions:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/40340425/87925660-86857180-ca78-11ea-9190-fce7e0086d38.png"><img src="https://user-images.githubusercontent.com/40340425/87925660-86857180-ca78-11ea-9190-fce7e0086d38.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">Deno version: <code class="notranslate">1.2.0</code>, Windows 10</p>