You can send arbitrary commands over the protocol fairly easily.
Main.sendOverProtocol('Emulation.setDeviceMetricsOverride', nexus5XMetrics());
Main.sendOverProtocol("Emulation.clearDeviceMetricsOverride");
// It returns a promise
{ style: 'unit', unit: 'millisecond', unitDisplay: 'narrow' } | |
┌─────────┬───────────┬─────────────────┬─────────────────┬───────┐ | |
│ (index) │ locale │ text │ browser │ same │ | |
├─────────┼───────────┼─────────────────┼─────────────────┼───────┤ | |
│ 0 │ 'af' │ '123,5 ms.' │ '123,5 ms.' │ true │ | |
│ 1 │ 'am' │ '123.5 ሚሴ' │ '123.5 ሚሴ' │ true │ | |
│ 2 │ 'ar' │ '١٢٣٫٥ ملي ث' │ '123.5 ملي ث' │ false │ | |
│ 3 │ 'as' │ '১২৩.৫ মিঃ ছেঃ' │ '123.5ms' │ false │ | |
│ 4 │ 'az' │ '123,5 msan' │ '123.5ms' │ false │ |
<head> | |
... | |
<meta name="viewport" content="width=device-width"> | |
... | |
</head> |
<html> | |
<head> | |
<script src="modifyme.js"></script> | |
</head> | |
<body> | |
<h1>Testing source map reloading.</h1> | |
<h3>Open Dev Tools and look in the console.</h3> | |
<p>Execute the <code>test_sm()</code> function and follow the source links.</p> | |
</body> | |
</html> |
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 |
USA = | |
{'name': 'data', 'children': [ | |
{'name':'A', 'desc':"Communicable, maternal, perinatal and nutritional conditions", 'children':[ | |
{'name':'A01', 'desc':"Tuberculosis", '90FE':0, '90FL':0, '90FP':.000484, '90F1':.000857, '90F5':.000954, '90F10':.000915, '90F15':.000679, '90F20':.001865, '90F25':.002201, '90F30':.002423, '90F35':.001872, '90F40':.001363, '90F45':.001124, '90F50':.000934, '90F55':.000866, '90F60':.000818, '90F65':.000846, '90F70':.00086, '90F75':.000809, '90F80':.000549, '00FE':0, '00FL':0, '00FP':.000539, '00F1':.001017, '00F5':.000981, '00F10':.000816, '00F15':.000609, '00F20':.001216, '00F25':.001175, '00F30':.001267, '00F35':.000935, '00F40':.000713, '00F45':.000735, '00F50':.000596, '00F55':.000584, '00F60':.000544, '00F65':.000565, '00F70':.000608, '00F75':.000603, '00F80':.000399}, | |
{'name':'A02', 'desc':"HIV/AIDS", '90FE':.023124, '90FL':.002457, '90FP':.023525, '90F1':.098902, '90F5':.103213, '90F10':.06633, '90F15':.078107, '90F20':.142801, '90F25':.114696, '90F30':.122893, '90F35' |
#!/bin/sh | |
echo " | |
Cool, let's start. | |
" | |
src=$PWD |
#Announcing The jQuery Standards Team
Today we're happy to announce the creation of a new jQuery sub-team called the jQuery Standards Team to give web developers to have a voice in the standards process.
##Introduction
We all know that web standards are important. They help ensure the code we write works across different technologies, for people of different abilities and most importantly across all browsers.
That said, how often do we all feel our voices, suggestions and ideas are heard by those groups responsible for defining these standards? The reality is that whilst many of us would like to see change, due to time restrictions and lengthy formal processes we're unable to participate in standards discussions, get involved with writing specifications and contribute to meetings about the future of features. This makes it difficult for web developers to have a voice.
/* | |
* matchMedia() polyfill - test whether a CSS media type or media query applies | |
* authors: Scott Jehl, Paul Irish, Nicholas Zakas | |
* Copyright (c) 2010 Filament Group, Inc | |
* MIT license | |
* dev.w3.org/csswg/cssom-view/#dom-window-matchmedia | |
* in Chrome since m10: http://trac.webkit.org/changeset/72552 | |
*/ |