/* #layout-container is the fixed full-viewport flex box holding the canvas bezel, the blue #canvas-message, #button-bar, the resize divider and the side panel. Hiding that one ancestor removes all of them at once; hiding #canvas-message alone would still leave the bezel and the black button bar on screen. Specificity here is (1 id) -- the same as the #layout-container rule in pfodCommon.css -- and this rule is later in document order, so it already wins. !important is belt-and-braces against any #layout-container rule added later in the stylesheet. */ #layout-container { display: none !important; } /* pfodCommon.css sets body{overflow:hidden} so the app itself never scrolls. <html> has no overflow rule (so it stays visible), which means body's hidden value propagates to the viewport and would clip this message on a phone. Put scrolling back, for the no-JS case only. Both elements are listed so the override still holds if <html> is ever given its own overflow rule. */ html, body { overflow: auto !important; background-color: #f4f4f4 !important; } /* Card matches pfodAlert() in connectionManager.js -- green title bar, white rounded panel, same shadow and metrics -- so a user with JS off still sees something recognisably pfodWeb. Normal flow (not position:fixed) so a long message scrolls naturally on a small screen. */ .nojs-card { font-family: 'Roboto', Arial, sans-serif; background-color: white; border-radius: 10px; box-shadow: 0 4px 20px rgba(0, 0, 0, 0.3); max-width: 560px; width: 90%; margin: 24px auto 40px auto; overflow: hidden; } .nojs-title { background-color: #4CAF50; color: white; padding: 15px 20px; font-size: 18px; font-weight: bold; } .nojs-body { padding: 20px; font-size: 14px; line-height: 1.6; color: #333; } /* Explicit margins/sizes: pfodCommon.css has no bare h1/h2/p/ol rules, so these would otherwise fall back to the browser's own defaults, which differ between engines. */ .nojs-body h1 { font-size: 20px; margin: 0 0 12px 0; color: #333; } .nojs-body h2 { font-size: 15px; margin: 18px 0 6px 0; color: #333; } .nojs-body p { margin: 0 0 12px 0; } .nojs-body ol { margin: 0 0 12px 0; padding-left: 22px; } .nojs-body li { margin: 0 0 4px 0; } .nojs-body code { font-family: Consolas, 'Courier New', monospace; background-color: #f0f0f0; padding: 0 3px; border-radius: 3px; } .nojs-note { color: #666; font-size: 13px; } /* Same footer convention as the connection prompt's header block. overflow-wrap keeps the long URL inside the card on a narrow phone instead of forcing a horizontal scrollbar. */ .nojs-footer { padding: 0 20px 16px 20px; color: #666; font-size: 12px; overflow-wrap: anywhere; }

pfodWeb

JavaScript is turned off

pfodWeb runs entirely in your browser. JavaScript is what talks to your pfod device and draws the menus, dials and charts, so with it turned off there is nothing to show and this page stays blank.

Turning it back on in Chrome

Open the Chrome menu (the three dots at the top right) and choose Settings.
Go to Privacy and security → Site settings → JavaScript.
Choose Sites can use JavaScript.
Come back to this page and reload it (Ctrl+R, or Cmd+R on a Mac).

If the address bar starts with file:/// you opened pfodWeb.html straight from disk. Chrome's per-site exception list does not accept file:/// addresses, so the setting above is the one that applies. If pfodWeb was instead loaded over http:// from your device or from pfodProxy, you can leave JavaScript off by default and allow it for that one address: click the icon at the left of the address bar, then Site settings → JavaScript → Allow.

Other browsers — Firefox: open about:config and set javascript.enabled to true. Safari: Settings → Security → tick Enable JavaScript.

Nothing you do in pfodWeb is sent to us — the page talks only to your own device.

pfodWeb Connection Setup

Select Target