| ########### | |
| # Pokemon GO Data Dump (in no order) | |
| # By Kaz Wolfe (@KazWolfe on gaming.stackexhange.com) | |
| # Dump version 3.3, pulled from 0.29.0 | |
| # | |
| # Feel free to use this dump in anything, but please link back to it! | |
| # This ensures that people can see and use the source of the data | |
| # (which updates regularly), and find out new things. | |
| # | |
| # Thanks Anonymous for some data: https://gist.github.com/anonymous/077d6dea82d58b8febde54ae9729b1bf |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Oppgave 1</title> | |
| <link rel="stylesheet" href="http://finncdn.no/bb/latest/css/so/so.min.css" /> | |
| </head> | |
| <body class="mal"> | |
| <h1>Oppgave 1</h1> | |
| <p>Skriv kode slik at knappen under endrer tekst til "Thank You!" når du klikker på den. Du skal ikke bruke jQuery eller andre biblioteker.</p> |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| /** | |
| * Note that this script is intended to be included at the *end* of the document, before </body> | |
| */ | |
| (function (window, document) { | |
| if ('open' in document.createElement('details')) return; | |
| // made global by myself to be reused elsewhere | |
| var addEvent = (function () { | |
| if (document.addEventListener) { | |
| return function (el, type, fn) { |