| 1 | <!DOCTYPE html> |
| 2 | <html lang="en"> |
| 3 | |
| 4 | <head> |
| 5 | <meta charset="utf-8"> |
| 6 | <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> |
| 7 | <meta name="theme-color" content="#000000"> |
| 8 | <!-- |
| 9 | manifest.json provides metadata used when your web app is added to the |
| 10 | homescreen on Android. See https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/ |
| 11 | --> |
| 12 | <link rel="manifest" href="%PUBLIC_URL%/manifest.json"> |
| 13 | <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico"> |
| 14 | <!-- |
| 15 | Notice the use of %PUBLIC_URL% in the tags above. |
| 16 | It will be replaced with the URL of the `public` folder during the build. |
| 17 | Only files inside the `public` folder can be referenced from the HTML. |
| 18 | |
| 19 | Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will |
| 20 | work correctly both with client-side routing and a non-root public URL. |
| 21 | Learn how to configure a non-root public URL by running `npm run build`. |
| 22 | --> |
| 23 | <script src="/react.development.js"></script> |
| 24 | <script src="/react-dom.development.js"></script> |
| 25 | <title>Expiration Example</title> |
| 26 | </head> |
| 27 | |
| 28 | <body> |
| 29 | <h1>Expiration Example</h1> |
| 30 | <p>This fixture demonstrates expiration using the |
| 31 | <code>timeout</code> option of |
| 32 | <code>requestIdleCallback</code>. If it's working correctly, you should see below a number that increments approximately once every second (the expiration |
| 33 | time of a low priority update.) If there is no counter, or if it increases too slowly or quickly, something is broken. |
| 34 | </p> |
| 35 | <noscript> |
| 36 | You need to enable JavaScript to run this app. |
| 37 | </noscript> |
| 38 | <div id="root"></div> |
| 39 | <!-- |
| 40 | This HTML file is a template. |
| 41 | If you open it directly in the browser, you will see an empty page. |
| 42 | |
| 43 | You can add webfonts, meta tags, or analytics to this file. |
| 44 | The build step will place the bundled scripts into the <body> tag. |
| 45 | |
| 46 | To begin the development, run `npm start` or `yarn start`. |
| 47 | To create a production bundle, use `npm run build` or `yarn build`. |
| 48 | --> |
| 49 | </body> |
| 50 | |
| 51 | </html> |