| // From https://ponyfoo.com/articles/var-let-const | |
| function toLargestUnit (value, unit = `MB`) { | |
| const units = [`MB`, `GB`, `TB`] | |
| const i = units.indexOf(unit) | |
| const nextUnit = units[i + 1] | |
| if (value >= 1024 && nextUnit) { | |
| return toLargestUnit(value / 1024, nextUnit) | |
| } | |
| return { value, unit } | |
| } |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| /* | |
| Alternative solution to switch statement or a suite of if statements | |
| using an object literal in JS to store cases. | |
| if (type == "save") { } | |
| if (type == "delete") { } | |
| */ | |
| function operation(type, opts) { | |
| var handler = { |
CSS Regions are now enabled by default in a widely used browser - Safari on iOS 7. This makes it easier for developers to experiment and use the feature in their projects.
Perhaps this is a good time to share some of the lessons we learned at Adobe while using CSS Regions in demos. Take this article as a recommendation of good practices, not by any means a comprehensive list. CSS Regions is still an evolving feature.
| (function(){ | |
| // feather-weight Modernizr-like CSS feature check | |
| ['shape-inside','flow-into','shiny-new-feature'].forEach(function(property){ | |
| // check if any variant exists, prefixed or not | |
| var isCapable = ['-webkit-','-ms-','-moz-',''].some(function(prefix){ | |
| return prefix + property in document.body.style | |
| }) | |
| property = isCapable ? property : 'no-' + property; |
This article is about building extensions for Google Chrome Developer Tools, also known as Chrome DevTools. Specifically, you'll learn how to work with element that is currently selected in the 'Elements' panel. Prior knowledge about DevTools extensions is required. Check out Boris Smus's Extending Chrome Developer Tools for an introduction and read through Google's own documentation on Chrome Extensions.
You can build extensions for the Google Chrome browser itself, which are targeted at regular users, as well as extensions for Chrome DevTools - the set of panels that developers use to inspect and audit content on web pages.
| function convertPixelPathToEm(path){ | |
| return path.trim().split(/,\s?/).map(function(pair){ | |
| return pair.trim().split(/\s+/).map(function(value){ | |
| value = parseInt(value, 10); | |
| value = (value === 0) ? 0 : (value / 16).toFixed(2) | |
| return value + 'em' | |
| }).join(' ') | |
| }).join(', ') | |
| } |
| /* | |
| Make sure the input element is the highest one in the page by z-index | |
| @param {DOM Element} el Element to stack at the top | |
| @param {DOM Element} ref BoundingClientRect reference of where to compare topl-left corner | |
| */ | |
| function stackOnTop(el, ref){ | |
| // elementFromPoint returns null if element is outside visible viewport | |
| // scroll the page so the element comes into view | |
| if (window.innerHeight < ref.top){ |