This week, I attended my now third W3CTPAC. After TPAC 2017 in Burlingame, CA, United States of America and TPAC 2018 in Lyon, France, TPAC 2019 was held in Fukuoka, Japan. For the first time, I felt like I could somewhat meaningfully contribute and had at least a baseline understanding of the underlying W3C mechanics. As each year, the TPAC agenda was crammed and overlaps were unavoidable. Below is the write-up of the meetings I had time to attend.
Day 1
On Monday, I attended the Service Workers Working Group (WG) meeting. The agenda this time was a mix of implementor updates, new proposals, and a lot of discussion of special cases. I know Jake Archibald is working on a summary post, so I leave it to him to summarize the day. Theraw meeting minutes are available in case you're interested.
Day 2
On Tuesday, I visited theWeb Application Security Working Group meeting as an observer. I was mostly interested in this WG because theagenda promised interesting proposals like Apple's/.well-known/change-passwordthat was met with universal agreement. Some interesting discussion also sparked around again Apple'sisLoggedIn() API proposal. I was reminded of why on the web we can't have nice things through an attack vector that leverages HSTS for tracking purposes. Luckily there isbrowser mitigation in place to prevent this.Themeeting minutes cover the entire day.
Day 3
Wednesday was unconference day with59(!) breakout sessions. Other than the at times tedious working group sessions,I find breakout sessions to be oftentimes more interesting and an opportunity to learn new things.
Breakout Session JS Built-in Modules
The first breakout session I attended was onJS built-in modules, a TC39 proposal by Apple for aJavaScript Built-in Library. The session's minutes are available, in general there was a lot of discussion and disagreement around namespaces and how built-in modules should be governed.
Breakout Session New Module Types: JSON, CSS, and HTML
The next session was onnew module types for JSON, CSS, and HTML. As the developer of<dark-mode-toggle>, I'm fully in favor of getting rid of the clumsyinnerHTML all the things!!!1! approach that vanilla JS custom elements currently make the programmer to follow. If you're likewise interested, subscribe to theCSS Modules issue and the HTML Modules issue in the Web Components WG repo. The discussion circulated mostly around details how @imports would work and how to convey the type of the import to avoid security issues, for example following the <link rel="preload"> way. The meeting minutes have the full details.
// Non-working example
import styles from 'styles.css' as stylesheet;
import settings from 'settings.json' as json;
Breakout Session Mini App Standardization
The Mini App Standardization session, organized by the Chinese Web Interest Group, was super interesting to me.In preparation of theGoogle Developer Days in Shanghai, China, that I spoke at right before TPAC, I havelooked at WeChat mini programs and documented the developer experience and how close to and yet how far from the web they are. A couple of days before TPAC, the Chinese Web Interest Group had released awhite paper that documents their ideas. The success the various mini apps platforms have achieved deserves our full respect. There were, however, various voices—including from theTAG—that urged the various stakeholders to converge their work with efforts made in the area ofProgressive Web Apps, for example around the Web App Manifest rather than create yet another manifest-like format. Read the full session minutes for all details. One of the results of the session was the creation of theMiniApps Ecosystem Community Group that I hope to join.
Breakout Session For a More Capable Web—Project Fugu
Together with Anssi Kostiainen from Intel andJohn Jansen from Microsoft,I organized a breakout session for a more capable web under the umbrella of Project Fugu 🐡. You can see our slides embedded below. In the session we argue that to remain relevant with native, hybrid, or mini apps, web apps, too,need access to a comparable set of APIs. We briefly touched upon the APIs being worked on by the cross-company project partners,and then opened the floor for an open discussion on why we see the browser-accessible web in dangerif we don't move it forward now,despite all fully acknowledged challenges around privacy, security, and compatibility. You can follow the discussion in the excellent(!) session minutes, courtesy of Anssi.
Day 4 and Day 5
Thursday and Friday were dedicated to the Devices and Sensor WG. The agenda was not too packed, but still kept us busy for one and a half days. We discussed almost from the start about permissions and how they should be handled. Permissions are a big topic in Project Fugu 🐡 and I'm happy that there's work ongoing in the TAG to improve the situation, including efforts around the Permissions API that is unfortunately not universally supported, leading to inconsistencies with some APIs having a static method for getting permission, others asking for permission upon the first usage attempt, and yet others to integrate with the Permissions API.For the Geolocation Sensor API, we agreed to try retrofitting expressive configuration of foreground tracking into the Geolocation API specification instead of doing it in Geolocation Sensor, which should improve vendor adoption. For geofencing and background geolocation tracking, we decided to explore Notification Triggers and Wake Locks respectively, which both weren't options when the work on Geolocation Sensor was started initially.
Maryam Mehrnezhad, an invited expert in the working group whose research is focused on privacy and security, presented on and discussed with us the implications on both fields that sensors potentially have and whether mitigation like accuracy bucketing or frequency capping are effective. The minutes capture the conversation well.
Finally, we changed the surface of the Wake Lock API hopefully for the last time. The previous changes just didn't feel right from a developer experience point of view, so better change the API while it's behind a flag than be sorry forever. I reckon I do feel sorry for the implementors Rijubrata Bhaumik and Raphael Kubo da Costa… 🙇
partial interface Navigator {
[SameObject] readonly attribute WakeLock wakeLock;
};
partial interface WorkerNavigator {
[SameObject] readonly attribute WakeLock wakeLock;
};
[Exposed=(Window,DedicatedWorker)]
interface WakeLock {
Promise<unsigned long long> request(WakeLockType type);
Promise<void> release(unsigned long long wakeLockID);
};
dictionary WakeLockEventInit {
required unsigned long long wakeLockID;
};
[Exposed=(Window,DedicatedWorker)]
interface WakeLockEvent : Event {
constructor(DOMString type, WakeLockEventInit init);
readonly attribute unsigned long long wakeLockID;
};
As a general theme, we "hardened" a number of APIs, for example decided to integrate geolocation with Feature Policy and now require a secure connection for the Battery Status API. The chairs Anssi and Reilly Grant have scribed the one and a half days brilliantly, the minutes for day 1 and day 2 are both online.
Conclusion
As I wrote in the beginning, TPAC slowly starts to feel like a venue where I can make some valuable contributions. Rowan Merewood put it like this in a tweet:
The biggest thing I'm learning at [#W3Ctpac] is if you want to change the web, it's a surprisingly small group of people you need to convince. The surrounding appearance of the W3C and all its language is intimidating, but underneath it's just other human beings you can talk to.
To which Mariko Kosaka fittingly responds:
[Y]]eah, but let's not forget getting to talk to that small set of people most often comes with being very, very, very privileged. […]
It's indeed a massive privilege to work for a company that has the money to take part in W3C activities, fly people across the world, and let them stay in five star conference hotels. With all the love for the web and all the great memories of a fantastic TPAC, let's not forget: the web is threatened from multiple angles, and being able to work in the standards bodies on defending it is a privilege of the few. Both shouldn't be the case.
Top comments (0)