UNPKG

litejs

Version:

Single-page application framework

130 lines (114 loc) 4.23 kB
<!DOCTYPE html> <html> <head> <!-- 1. https://blog.whatwg.org/the-road-to-html-5-character-encoding 2. Options: resize enabled: width=device-width,initial-scale=1 resize denied: width=device-width,initial-scale=1,maximum-scale=1 3. Since Chrome 31. Chrome temporarily accepts the usage of "apple-mobile-web-app-capable" Meta tag apple-touch-fullscreen behave the same way as apple-mobile-web-app-capable. Only the last one is mentioned in Safari documentation, so I would stick with it. It looks to me as if apple-touch-fullscreen was used in early demos/previews, so it was left working later when the SDK got actually released, but the preferred version is the one documented. 4. Since Chrome 39 you can use Web App Manifest. http://www.w3.org/TR/appmanifest/ If there's a manifest with display specified, "mobile-web-app-capable" is ignored. --> <meta charset="UTF-8"> <!-- 1 --> <meta name="viewport" content="initial-scale=1,maximum-scale=1"> <!-- 2 --> <meta name="mobile-web-app-capable" content="yes"> <!-- 3 --> <link rel="manifest" href="manifest.json"> <!-- 4 --> <!-- <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-status-bar-style" content="black"> <link rel="apple-touch-startup-image" href="/startup.png"> --> <!-- OpenSearch autodiscovery: http://www.opensearch.org/Specifications/OpenSearch/1.1 <link rel="search" type="application/opensearchdescription+xml" href="http://example.com/content-search.xml" title="Content search"> --> <!-- Turn off telephone number detection in Safari on iOS, you can still use the "tel" URI scheme. <meta name="format-detection" content="telephone=no"> --> <!-- Remove tap highlight in IE10 and IE11 on Windows Phone. <meta name="msapplication-tap-highlight" content="no"> --> <!-- Chrome, Firefox OS and Opera <meta name="theme-color" content="#4285f4"> --> <!-- <meta http-equiv="x-dns-prefetch-control" content="off"> To be sure you're using the latest rendering mode for IE. The best practice is an X-UA-Compatible HTTP Header. <meta http-equiv="X-UA-Compatible" content="IE=edge"> Meta-tags that attempt to apply the X-Frame-Options directive DO NOT WORK. You must apply the X-Frame-Options directive as HTTP Response Header. X-Frame-Options: deny Content-Security-Policy: script-src 'self'; frame-src 'none' Strict-Transport-Security: max-age=778000 --> <!-- Fallback application metadata for legacy browsers --> <meta name="application-name" content="App"> <meta name="msapplication-tooltip" content="App"> <title>App</title> <!-- <base href="/"> --> <!-- Place icons in the root of your domain and these references are not needed. <link rel="shortcut icon" href="favicon.ico"> <link rel="apple-touch-icon" href="apple-touch-icon.png"> --> <link rel="stylesheet" href="lib.css" min="m.css?{hash}" require=" litejs/css/base.css %/grid.css %/spacing-4.css "> <link rel="stylesheet" href="app.css" min> </head> <body> <!-- Include scripts in the end of the body, so there is no need for waiting DOMContentLoaded --> <script src="js/load.js" require="litejs/ui/load" inline></script> <script src="js/up.js" min="0.js?{hash}" banner="litejs.com/MIT-LICENSE.txt" if="!Object.assign" require=" litejs/ui/polyfill/es5 "></script> <script src="js/litejs.js" min="1.js?{hash}" banner="litejs.com/MIT-LICENSE.txt" require=" litejs/ui litejs/model "></script> <script src="view/components.tpl" type="litejs/view" require=" litejs/ui/component/confirm.tpl "></script> <script src="view/main.view" type="litejs/view"></script> <script src="js/app.js" min></script> <noscript> <h1>Error</h1>This application requires JavaScript <!-- Redirect to no-JavaScript version of the site or provide a link to give a chance to turn JavaScript on before redirect. <meta http-equiv="refresh" content="0;url=no-js.html"> --> </noscript> </body> </html>