| if(!window.Promise) { | |
| var req = new XMLHttpRequest(); | |
| req.open('GET', 'https://cdn.polyfill.io/v2/polyfill.min.js?features=Promise', false); | |
| req.send(); | |
| eval(req.responseText); | |
| } |
| -149.8935557,61.21759217,Starbucks - AK - Anchorage 00001,"601 West Street_601 West 5th Avenue_Anchorage, Alaska 99501_907-277-2477" | |
| -149.9054948,61.19533942,Starbucks - AK - Anchorage 00002,"Carrs-Anchorage #1805_1650 W Northern Lights Blvd_Anchorage, Alaska 99503_907-339-0500" | |
| -149.7522,61.2297,Starbucks - AK - Anchorage 00003,"Elmendorf AFB_Bldg 5800 Westover Avenue_Anchorage, Alaska 99506" | |
| -149.8643361,61.19525062,Starbucks - AK - Anchorage 00004,"Fred Meyer - Anchorage #11_1000 E Northern Lights Blvd_Anchorage, Alaska 995084283_907-264-9600" | |
| -149.8379726,61.13751355,Starbucks - AK - Anchorage 00005,"Fred Meyer - Anchorage #656_2300 Abbott Road_Anchorage, Alaska 99507_907-365-2000" | |
| -149.9092788,61.13994658,Starbucks - AK - Anchorage 00006,"Fred Meyer - Anchorage (Dimond) #71_2000 W Dimond Blvd_Anchorage, Alaska 995151400_907-267-6700" | |
| -149.7364877,61.19533265,Starbucks - AK - Anchorage 00007,"Safeway-Anchorage #1817_7731 E Northern Lights Blvd_Anchorage, Alaska 99504_907-331-1700" | |
| -149.8211,61.2156 |
| (function(){ | |
| if(document.querySelector("#_CRIT_CSS")){return;} | |
| var container = document.createElement("div"); | |
| container.id = "_CRIT_CSS"; | |
| container.innerHTML = '<textarea cols=80 rows=20></textarea><button id="CRIT_FIND">Find Critical CSS</button><button id="CRIT_CLOSE">Exit</button>'; | |
| container.style.position = "fixed"; | |
| container.style.top = 0; | |
| container.style.left = 0; | |
| container.style.right = 0; | |
| container.style.backgroundColor = "#FFF"; |
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
| /** | |
| * Fix for vw, vh, vmin, vmax on iOS 7. | |
| * http://caniuse.com/#feat=viewport-units | |
| * | |
| * This fix works by replacing viewport units with px values on known screen sizes. | |
| * | |
| * iPhone 6 and 6 Plus cannot run iOS 7, so are not targeted by this fix. | |
| * Target devices running iOS 8+ will incidentally execute the media query, | |
| * but this will still produce the expected result; so this is not a problem. |
| # alias radio='function __radio(){ r=`grep -v "#" radios_nacionales.txt | grep -m 1 -i $1 | cut -d" " -f1`; cvlc $r 2> /dev/null; }; __radio' | |
| # podria utilizarse mplayer en vez de vlc | |
| AMs Nacionales | |
| http://cdn.instream.audio:9288/stream Radio Madre 530 | |
| https://streaming1.hostingmontevideo.com:7019/; Radio Colonia 550 | |
| http://server.laradio.online:25224/live.mp3 Radio Argentina 570 | |
| http://playerservices.streamtheworld.com/api/livestream-redirect/CONTINENTAL_SC Continental 590 | |
| https://streammax.alsolnet.com/radiorivadavia Rivadavia 630 |
| let hasBlobConstructor = typeof(Blob) !== 'undefined' && (function () { | |
| try { | |
| return Boolean(new Blob()); | |
| } catch (e) { | |
| return false; | |
| } | |
| }()); | |
| let hasArrayBufferViewSupport = hasBlobConstructor && typeof(Uint8Array) !== 'undefined' && (function () { | |
| try { |
This method avoids merge conflicts if you have periodically pulled master into your branch. It also gives you the opportunity to squash into more than 1 commit, or to re-arrange your code into completely different commits (e.g. if you ended up working on three different features but the commits were not consecutive).
Note: You cannot use this method if you intend to open a pull request to merge your feature branch. This method requires committing directly to master.
Switch to the master branch and make sure you are up to date:
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
| (function () { | |
| var perfBar = function(budget) { | |
| window.onload = function() { | |
| window.performance = window.performance || window.mozPerformance || window.msPerformance || window.webkitPerformance || {}; | |
| var timing = window.performance.timing, | |
| now = new Date().getTime(), | |
| output, loadTime; |
