You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike other API doc pages, like the WASI page, the Web Crypto doc page is not responsive on mobile. Self-explanatory.
Here are my failed attempts at fixing:
At first, I immediately thought it would be a problem inside the <head> tag. The page looked suspiciously zoomed out, like when it doesn't have <meta name="viewport" content="width=device-width, initial-scale=1">. Changing it wielded no results.
So I decided to actually get familiar with the build process for the API docs, and found out it injects media queries in a <style> tag. Tried manually changing the media queries of the affected page with one from a working page, didn't work.
I suppose I'm missing something in the build process that could be causing this problem. Tried investigating how the Markdown files are processed, but couldn't find much that could pinpoint the root cause.
The text was updated successfully, but these errors were encountered:
Affected URL(s)
https://nodejs.org/docs/latest/api/webcrypto.html
Description of the problem
Unlike other API doc pages, like the WASI page, the Web Crypto doc page is not responsive on mobile. Self-explanatory.
Here are my failed attempts at fixing:
At first, I immediately thought it would be a problem inside the
<head>
tag. The page looked suspiciously zoomed out, like when it doesn't have<meta name="viewport" content="width=device-width, initial-scale=1">
. Changing it wielded no results.So I decided to actually get familiar with the build process for the API docs, and found out it injects media queries in a
<style>
tag. Tried manually changing the media queries of the affected page with one from a working page, didn't work.I suppose I'm missing something in the build process that could be causing this problem. Tried investigating how the Markdown files are processed, but couldn't find much that could pinpoint the root cause.
The text was updated successfully, but these errors were encountered: