サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
衆院選
paul.kinlan.me
I forgot that Scroll to Text fragment was a thing that is launching soon in Chrome (81 and not 80 as mentioned in Chrome Status), until I saw this Tweet. I love this feature, it let's you link to more than just named elements. Domenic Denicola asked if there was an extension that did this. I don't think you need one, because bookmarklets are awesome and underused. I decieded that it should be pret
I just wanted to spend a couple of moments talking about some of the events over the last couple of days that we're ultimately caused by me. Before I get into what happened, I just wanted to say sorry to the Safari team over at Apple for any frustration they have with what we shared at Chrome Dev Summit. I'm sorry for the misrepresentation of Safari Tech Preview's compatibility score for the Compa
Looks like one of the oldest bugs in Chromium has been fixed. Chrome used to display images in landscape orientation even if they were taken in portrait on a phone. Now it appears that in Chrome 81 we will respect the image orientation from the files EXIF data and display the image in that orientation by default unless you override it with a CSS attribute image-orientation: none. Fun times. Demo I
It would be an understatement to say that MDN's Developer Needs Assessment has helped the Chrome Web Platform team prioritise their work for 2020, in fact it's been central to DevRel and the Web Platform teams objective setting (more on that soon). Over the last year or so we've been fortunate to collaborate with the MDN team via the PAB (Product Advisory Board), and during that time we've been th
PWA. Progressive Web Apps. Frances Berriman and Alex Russell coined the term "progressive web apps" in 2015 with what I think is a seminal post "Progressive Web Apps: Escaping Tabs Without Losing Our Soul". 3 years later, we've come a long way. From a loose collection of technologies - Service Worker, Manifest, Add to Homescreen, Web Push - that were originally only implemented in one browser engi
This is a script that Eric Bidelman gave me (or helped me create — I can quite recall). I needed a simple way to host a custom web app that could connect to an instance of Headless Chrome over the Puppeteer API. This article is mostly a reference for the future. The docker container is relatively straight forward: Use node:8-slim Install all the required dependencies, including Chrome. Initialize
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 oth
I like Progressive Web Apps. I like the model it offers for how you build good, solid, reliable web sites and apps. I like the principle platform API - service worker - that enables the PWA model to work. One of the traps that we have fallen into is "App Shell". The App Shell model says that your site should present a complete shell of your application (so that the experience something even when y
I was at the party of the Chrome Dev Summit and Miguel Casas-Sanchez on the Chrome team came up to me and said "Hey Paul, I have a demo for you". Once I saw it, I had to get it into my talk. That API was the Shape Detection API that is currently in the WICG in an incubation and experimentation phase and is a nice incremental addition to the platform. The Shape Detection API is interesting because
Last year just before the Chrome Dev Summit, Miguel Casas came up to me and showed me something that blew my mind: Face Detection in the browser using the Shape Detection API. Shortly after that Barcode Detection was added that allowed me to update my QR Code scanner so that I no longer had to include a massive (albeit awesome) port of a QR scanning library. The Shape Detection API is still in dev
I am an ardent believer in The Headless Web, that is the interaction points that your users will have with the web will not be in the traditional browser but deeply integrated on the users device via things like notifications and cards, in webviews and services, and on new types of devices and in ways that we can't yet imagine and as a developer all you do is build for the web. It will still be po
I like Web Components. It has taken a long time to get here but things are moving in the correct direction with Safari shipping Shadow DOM and now landing support for Custom Elements. I've been thinking a lot recently about Web Components, that is custom elements, template, Shadow DOM and CSS variables, specifically I have been focusing some of my thoughts on custom element space and how this can
Many of you know that I am passionate about inter-app communications, specifically the action of sharing. One of the things that I have encouraged anyone who wants to do the next version of Web Intents to do is focus on a very small and specific use case. Well Good News Everybody. Matt Giuca on the Chrome team has been working on a simple API (Web Share) that has the potential to connect websites
In 2014 I was honoured to speak at Fronteers in Amsterdam (I would heartily recommend it). I was attempting to talk about the state of the web platform, where it was, where it is, and where it will be. Where it is, I've partly covered recently in The Lumpy Web. It covers the state of inconsistent feature support and the pain that it can cause developers. Where it (the web) will be, I touched on br
TL;DR - Here is a demo Code Our team has built a lot of Progressive Web Apps recently to demonstrate how we think they can be built: Airhorner, Voice Memos, Guitar Tuner, SVG-OMG are a few that spring to mind. One thing that is common across all of these sites is that they have no server component to store and synchronise data. We built these sites as examples and reference implementations of the
There have been a lot of conversation about all the issues of the web over the last couple of weeks and they broadly group themselves into the following categories: Performance Lumpy inconsistent browsers Rapidly expanding feature landscape. I want to put these to the side for a couple of minutes to quickly talk about one of terms that we have used in Google to quickly describe the positive aspect
Is your site on HTTPS? No? Do you know if any ISP's or other services are injecting Ads or anything else in to your site? No. I thought not. I don't either... well, maybe until now. TL;DR It's incredibly hard to detect if an ISP is manipulating your site, however it is relatively easy to aggregate many of the content injections occurring across your site. As a publisher of content you should be co
SMS is dying. WhatsApp, Line, WeChat, SnapChat and many others are making it easier to talk to friends, families and groups. A common feature across these apps is: They are all on native platforms and are on the web only to drive users to their native app install pages. I have spoken to a lot of developers about why their apps are only on native platforms, and to users about the features that they
I get a huge number of questions from web developers wanting to know exactly what happened to the Web Intents. This is my recollection. I don't feel bitter; I am just disappointed. It was my first big project failure and at the time it hurt when it got canned. About 6 months ago I sent an email to the DAP — the working group that was one of the hosts of the Web Intents task force — that I think sh
Page Speed Insights for Mobile launched the other week. It’s a tool that analyses your site in the context of a mobile device and tells you what you need to do to improve the network performance of the site. In about an hour I had taken 3 seconds off my blogs page load time by removing JS files and adding Caching (doh!) and crunching PNGs (double doh!), going from a score of about 34 to 84. One of
Let me start by saying it is not possible. But I have a half solution. If you have tried to install Chrome for Android before on an emulator you will be intimately familiar with the series of errors that occur, most noteably: Arghhh... I am not going to document how you get this far because I will just be spreading alot of useless facts that ultimately lead you nowhere... The problem stems from th
We have a huge problem on the web today. If I built an image gallery application and I wanted to let users edit an image so that they can remove red-eye from a photo I either have to build an application that edits the images, or integrate with a 3rd party solution. Doing this is hard and stops you from building an awesome image gallery; and what happens if the user has a favorite service that the
このページを最初にブックマークしてみませんか？
『paul.kinlan.me』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
