Vysor lets you view and control your Android on your computer. An easy install Chrome app, compatible with all operating systems.
In the news today: a link which, when moused over or clicked on, crashes Google Chrome. It’s a heck of a bug: but how does it work, and what does it have to do with “null-terminated strings”?
An attack known as Double Encoding
The idea of the virtual viewport is to split the notion of “the viewport” into two, “the layout viewport” (where fixed position items are attached) and “the visual viewport” (What the users actually see).
In the screenshots above you can cleary see this in action: without a virtual viewport it’s not possible to view right hand side of the menu (which is
position: fixed;) when zoomed in. With the virtual viewport this is possible.
This presentation will clarify some things:
The latest version of Canary now has controls to globally slow down and pause animation right from Dev Tools. It’s such a huge help for both designing and troubleshooting your animations.
Let me introduce what I call the Chrome DevTools App. It’s a standalone app that runs Chrome DevTools in its own process. It’s powered by node-webkit, and it’s able to run on Windows, Mac and Linux, completely independently of Chrome.
From the same guy who brought/is bringing us RemoteDebug.
My name is Bramus and I approve this message:
We, the Chrome Security Team, propose that user agents (UAs) gradually change their UX to display non-secure origins as affirmatively non-secure. We intend to devise and begin deploying a transition plan for Chrome in 2015. The goal of this proposal is to more clearly display to users that HTTP provides no data security.
It soon will be 2015, time to embrace HTTPS.
Note: Running WordPress? This guide on how to migrate from HTTP to HTTPS has got you covered.
Over the weekend an important set of commits (this one amongst others) landed in Chromium, enabling Emoji in Chrome on OS X, and – after 4 years – marking the bug “Emoji does not display in webpage contents on OS X Lion+” as
When using Canary, things like The Pile Of Poo Test will work just fine from now on 🙂
The ios_webkit_debug_proxy allows developers to inspect MobileSafari and UIWebViews on real and simulated iOS devices via the DevTools UI and WebKit Remote Debugging Protocol. DevTools requests are translated into Apple’s Remote Web Inspector service calls.
The proxy detects when iOS devices are attached/removed and provides the current device list on http://localhost:9221. A developer can click on a device’s link (e.g. http://localhost:9222) to list that device’s open tabs, then click on a tab link (e.g. http://localhost:9222/devtools/page/1) to inspect that tab in their browser’s DevTools UI.