{"version":3,"file":"modal-product-guide-section.min.js","mappings":"wZA+BA,SAASA,EAA6BC,GACpC,MAAMC,EAAQC,SAASC,cAA4B,wBAEnD,GAAKF,EAAL,CAKA,IAAK,MAAMG,KAAaH,EAAMI,iBAA8B,iBACtDD,EAAUE,KAAON,EAAMO,OAAOC,WAChCJ,EAAUK,QAAS,EACnBR,EAAMS,QAAQC,MAAQP,EAAUM,QAAQC,OAExCP,EAAUK,QAAS,EAIvBR,EAAMS,QAAQE,KAAO,MAXrB,MAFEC,QAAQC,KAAK,wCAcjB,ECSO,SAAeC,EACpBC,GACA,QAD2B,IAA3BA,IAAAA,EAA8B,oBACF,aAAxBd,SAASe,YAAuC,qBAATD,GACjB,gBAAxBd,SAASe,WAA+B,CACxC,MAAMC,EAAQC,WAAWJ,EAAU,GAEnC,MAD8B,IAAMK,aAAaF,EAEnD,CACEG,iBAAiBL,EAAMD,EAI3B,CDfAO,CAJA,WACED,iBAAiB,gCAAiCtB,EACpD","sources":["webpack://lange/./sections/modal-product-guide/index.ts","webpack://lange/./lib/dom-ready.ts"],"sourcesContent":["import { ready } from '../../lib/dom-ready.js';\n\n// The modal-element around the product guides handles the close button, the dismiss gestures, and\n// telling the modal manager when it opens and closes. We pick which guide shows, give the modal\n// that guide's title, and open it.\n\ntype ModalElement = HTMLElementTagNameMap['modal-element'];\n\n/**\n * This event causes the product guide modal window to show up\n */\ntype ProductGuideModalRequestedEvent = CustomEvent<{\n  /**\n   * The id of the content section to reveal. The modal holds several content sections as direct\n   * children, each identified by its own id and hidden by default. The handler reveals the section\n   * whose id matches this value and hides the others, so this effectively selects which part of the\n   * guide the modal opens to.\n   */\n  contentId: string;\n}>;\n\ndeclare global {\n  interface WindowEventMap {\n    'product-guide-modal-requested': ProductGuideModalRequestedEvent;\n  }\n}\n\n/**\n * Show the product guide modal. It may contain multiple content sections, so the contentId property\n * is used to determine which section should be visible when the modal is opened\n */\nfunction onProductGuideModalRequested(event: ProductGuideModalRequestedEvent) {\n  const modal = document.querySelector<ModalElement>('#product-guide-modal');\n\n  if (!modal) {\n    console.warn('product guide modal element not found');\n    return;\n  }\n\n  for (const contentEl of modal.querySelectorAll<HTMLElement>(':scope > [id]')) {\n    if (contentEl.id === event.detail.contentId) {\n      contentEl.hidden = false;\n      modal.dataset.title = contentEl.dataset.title;\n    } else {\n      contentEl.hidden = true;\n    }\n  }\n\n  modal.dataset.open = 'true';\n}\n\nfunction onReady() {\n  addEventListener('product-guide-modal-requested', onProductGuideModalRequested);\n}\n\nready(onReady);\n","/**\n * Releases the handle returned from the ready() function.\n *\n * This is idempotent. Additional calls are pointless but harmless.\n */\nexport type ReleaseHandle = () => void;\n\n/**\n * A subset of events that pertain to document ready state.\n */\ntype LoadingEventMap = Pick<DocumentEventMap, 'DOMContentLoaded' | 'load'>;\n\n/**\n * Calls the provided callback when the document is ready. This works both when the document is\n * already ready and when it is not, so callers do not have to care. This exists because it ensures\n * that each caller consistently expresses its dependency on document readiness, and to save a bit\n * of boilerplate.\n *\n * A document is considered ready when it has been parsed. This corresponds to the ready state of\n * 'interactive'. When the document has been fully loaded, the ready state is 'complete'. The\n * callback runs either way, so callers do not have to check which one they are in.\n *\n * Ready means the html is parsed and the DOM is there to query. It does not mean the page's other\n * scripts have run. Deferred scripts and module scripts run after the ready state turns\n * 'interactive' and before DOMContentLoaded fires, so a callback here can run before them. When a\n * caller needs some other script to have run already, this is the wrong tool, and it should wait on\n * whatever that script produces instead.\n *\n * That remedy has a catch of its own when the calling bundle is loaded with async. An async bundle\n * can execute after DOMContentLoaded has already fired, so a plain listener for that event never\n * runs and the work silently never happens. Nothing here can detect that, because by the time this\n * file executes the event is long gone. Catching it needs something registered at parse time,\n * before any bundle loads.\n *\n * There is a second trap right next to that one, and it applies only when waiting for\n * DOMContentLoaded. The ready state stays 'interactive' after DOMContentLoaded has fired, all the\n * way until 'complete', so the ready state cannot tell you whether DOMContentLoaded is still coming\n * or has already gone. Waiting for load is not exposed to this, because the ready state turns\n * 'complete' and load fires in the same task, so seeing 'complete' means load has fired too.\n *\n * When the document is already ready, the callback is invoked via setTimeout. This way, if the\n * callback throws, the error surfaces to the global error handler in a way that is similar to what\n * happens when an event listener throws.\n *\n * We might one day want to move this to an NPM library.\n *\n * Beware of a quirk here. setTimeout yields, and the busier the frontend, the longer it takes to\n * fire. Page load is exactly when the frontend is busiest. The timeout is a floor and not a\n * guarantee, so there is no real bound on how long that yield lasts. What this means is that using\n * this library can introduce more delay than you might expect. Compare code that runs on async load\n * and checks ready state and invokes immediately to code that runs after setTimeout. The former\n * runs in the same tick, the latter runs in \"some later tick\". That later tick can be surprisingly\n * much later. That can cause initial paint issues.\n *\n * @see https://developer.mozilla.org/en-US/docs/Web/API/Document/readyState\n * @see https://developer.mozilla.org/en-US/docs/Web/API/Document/DOMContentLoaded_event\n * @see https://html.spec.whatwg.org/multipage/parsing.html#the-end\n */\nexport function ready(callback: (event?: Event) => void,\n  type: keyof LoadingEventMap = 'DOMContentLoaded') {\n  if (document.readyState === 'complete' || (type === 'DOMContentLoaded' &&\n    document.readyState === 'interactive')) {\n    const timer = setTimeout(callback, 0);\n    const handle: ReleaseHandle = () => clearTimeout(timer);\n    return handle;\n  } else {\n    addEventListener(type, callback);\n    const handle: ReleaseHandle = () => removeEventListener(type, callback);\n    return handle;\n  }\n}\n"],"names":["onProductGuideModalRequested","event","modal","document","querySelector","contentEl","querySelectorAll","id","detail","contentId","hidden","dataset","title","open","console","warn","callback","type","readyState","timer","setTimeout","clearTimeout","addEventListener","ready"],"sourceRoot":""}