Mustafa for Google Chrome, on Dev-Channel writes,
The Gestalt principles are a series of laws that are used to explain why human beings naturally find organized patterns in objects they see around them. The goal with the principles was to explain why we group objects in some ways but not others.
There are many different principles, but here I am going to look at the ones that effect grouping, these are; proximity, similarity, common fate, continuity, closure, and prägnanz.
Share Target API is now in Chrome breaking down one of the last silos of native platforms
Use onappinstalled to detect when a progressive web app is installed.
A simple bookmarklet that will performance trace the current page and open in an hosted devtools instance
A simple docker container that can host an instance of puppeteer and a custom app.
CSP nonce values can help you securely run inline content on you site. But it can be hard to get it working with Service Workers... until now.
If we are to build HTML in Workers then we need some 'DOM' in them.
Templating libraries needn't be so hard
Summary of the challenges that I beleive we developers face every day.
This article is over a year late. It was stuck in my drafts for a long time, yet I think the idea is something that we need to solve into 2018. It also turns out that other issues have arisen in the last year that make it a bit more relevant. I was in Indonesia earlier in 2016 idly chatting with developers and it came up in conversation that the web is screwed (they were the literal words).
What is this? This is my Software Engineering final year project for University from about 2003. I used to be work in the Fraud Detection industry (mortgage and credit card fraud) and this project was to solve a problem that I had found in the telecoms industry: fraudulent phone calls. It was impossible (for me) to get phone records from telecoms companies, so I had to build a tool that would model fraudulent calls and normal call patterns, I then had to build a tool that would detect calls that were fradulent from all of the call records.
Michael Mahemoff taught me a lot about the possibilities of the web. Prior to working with Mike I built on the web and I understood the benefits such as linkability and discovery, but I never really had a full picture of what would be possible. One thing that Mike said was “the Web is my API”, where he talked about the being able to expose your site and your data in a page via microformats and other structured data and being able to access it directly from another another browser context, using a simple XMLHttpRequest and the CORS API:
I never got over the death of Web Intents. I always felt that there is still a serious problem on the web, we build silos that lock the user into one web site and we don’t connect our apps together to build richer experiences. We have links that allow us to navigate to another site, but we don’t connect our apps to functionality that we can use in our sites.
It's nearly impossible to get consistent get data in and out of a web app on the client
How should Web and Chrome Developer Relations work?
Building Progressive Web Apps progressively is possible. This is how I did it.
I couldn't find an easier way, so I built it myself
Custom Elements need clear and parsable API documentation.
This little doozey hit me, so I'm documenting incase anyone else has the same issue