> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/general/browser-support-policy.md). # Browser Support Policy At DoctorLogic, we’re committed to developing and maintaining best-in-class website experiences for all users. Our design and engineering teams strive to leverage modern web standards, capabilities, performance, and security features available exclusively in modern, up-to-date browsers. ![](https://2741824567-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAUTtHOF4cY8fyDoNkF%2F-LX6-HKEjuz_O_AcptSm%2F-LX65kNpYjXG5TKV1YGW%2Fbrowser.png?alt=media\&token=003c9483-f639-40c2-b253-56a33c585f04) Our Websites Product includes support for the current and previous releases of [Chrome](https://www.google.com/chrome/), [Firefox](https://www.firefox.com/), [Edge](https://www.microsoft.com/en-us/windows/microsoft-edge), and [Safari](https://www.apple.com/safari/) on a rolling basis. We support desktop, smartphone, tablet versions (devices) of these respective browsers on the Windows, Mac, iOS, and Android platforms. Each time a new version is released, we begin supporting that version and stop supporting the third most recent version. We re-perform our browser testing for each release cycle. In the event we discover compatibility issues related to supported browsers, our team will work expeditiously to remedy in coordination with browser vendors and/or hosting providers. For an optimal experience, we recommend that users enable/allow browser support for cookies, images, HTML5 video, CSS, and JavaScript. Our team regularly analyzes browser usage data both on our user-base and across the healthcare industry. We also review the status of browser products to ensure they are being actively maintained and are releasing enhanced support for web and security standards. \ \ For non-supported browsers (included non-supported devices or platforms) aspects of a page's layout, design, and/or interactivity may be degraded. In rear cases, older browser may lack critical security capabilities needed to verify a TLS certificate and our server may not allow a user to submit forms or access certain pages or components of a page. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.doctorlogic.com/docs/general/browser-support-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.