I've heard this before:
What I really get frustrated by is that I cannot wrap
console.*and preserve line numbers
We enabled this in Chrome DevTools via blackboxing a bit ago.
If you blackbox the script file the contains the console log wrapper, the script location shown in the console will be corrected to the original source file and line number. Click, and the full source is looking longingly into your eyes.
| var Chrome = require('chrome-remote-interface') | |
| Chrome({ | |
| chooseTab: function(tabs) { | |
| var idx = 0 | |
| tabs.forEach(function(tab, i) { | |
| if (tab.url === 'http://localhost:9966/') | |
| idx = i | |
| }) | |
| return idx |
I hereby claim:
To claim this, I am signing this object:
| # Build arguments for the gn build | |
| # You can set these with `gn args out/Default` | |
| # ( and they're stored in src/out/Default/args.gn ) | |
| # See "gn args out/Default --list" for available build arguments | |
| # component build, because people love it | |
| is_component_build = true | |
| # release build, because its faster | |
| is_debug = true |
I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).
Before I get into this, I should point out that if you have jQuery on your page, when you type $ in your console it's indeed jQuery, otherwise, it's defined by your developer tools.
A bit ago, someone on SO asked where does $$() come from? Alex Russell called this "the bling-bling function", and it's part of the Command Line API and will return an array of elements to match a CSS selector. Why the double $$? Well, the single $ was already taken: the pioneer of developer tools, Firebug, assigned the $() to getElementById and so it has remained.
But.. let's be real though, ID's? Who is using ID's anymore? Using $ and $$ I often tho
I wrote this in early January 2012, but never finished it. The research and thinking in this area led to a lot of the design of Yeoman and talks like "Javascript Development Workflow of 2013", "Web Application Development Workflow" and "App development stack for JS developers" (surpisingly little overlap in those talks, btw).
Now it's June 2013 and the state of web app tooling has matured quite a bit. But here's a snapshot of the story from 18 months ago, even if a little ugly and incomplete. :p
A timeline of the last four years of detecting good old window.localStorage.
October 2009: 5059daa
| // starting with current element, look up the DOM ancestor tree to see if anything matches the given selector | |
| // returns element if found | |
| // returns false if not found | |
| function closest(elem, selector) { | |
| var matchesSelector = elem.matches || elem.webkitMatchesSelector || elem.mozMatchesSelector || elem.msMatchesSelector; | |
| while (elem) { |
| // @license http://opensource.org/licenses/MIT | |
| // copyright Paul Irish 2015 | |
| // Date.now() is supported everywhere except IE8. For IE8 we use the Date.now polyfill | |
| // github.com/Financial-Times/polyfill-service/blob/master/polyfills/Date.now/polyfill.js | |
| // as Safari 6 doesn't have support for NavigationTiming, we use a Date.now() timestamp for relative values | |
| // if you want values similar to what you'd get with real perf.now, place this towards the head of the page | |
| // but in reality, you're just getting the delta between now() calls, so it's not terribly important where it's placed |