975: What’s Missing From the Web Platform?

February 2, 2026

50 min episode · 2 min read

Scott Talinski

Episode

50 min

Read time

2 min

AI-Generated Summary

Published Feb 3, 2026

Key Takeaways

✓Customizable Select Element: The web platform now provides a customizable select element allowing full CSS control while maintaining accessibility and keyboard navigation without JavaScript dependencies. This primitive enables developers to style dropdowns completely, with combo box and multi-select variants currently in development, eliminating the need for heavy third-party component libraries for basic UI patterns.
✓Cookie Consent API Necessity: The web desperately needs standardized browser APIs for cookie consent management to replace the current mess of poorly coded banners with dark patterns. A native consent API would store user preferences directly in the browser, eliminating repetitive popups across sites. Sentry exemplifies best practices by removing all tracking cookies from their website, requiring consent banners only for embedded content like YouTube videos.
✓TypeScript Native Integration: TypeScript has become the de facto standard for JavaScript development, with proposals for types-as-comments allowing browsers to ignore type annotations rather than execute them. Node already supports running TypeScript files natively without transpilation. The browser vendors are taking time to evaluate the approach rather than rushing implementation, learning from past mistakes like premature jQuery standardization attempts.
✓Local AI Model Access: Future browser APIs should enable access to device-native AI models for private, free inference while allowing developers to swap in custom models or external APIs. This approach would enable instant natural language processing for tasks like parsing date inputs, validating postal codes, and fixing common form errors without sending data externally or incurring API costs per request.
✓Reactive Templates as Primitives: Browsers need native reactive templating where variables automatically update DOM elements when changed, eliminating the need for framework overhead in simple applications. Currently developers must either use full frameworks or manually create rerender functions. This primitive would enable lightweight interactive applications without installing React, Vue, or similar libraries for basic state-to-DOM synchronization patterns.

What It Covers

Wes Bos and Scott Tolinski examine missing features from the web platform, covering needed UI primitives like customizable selects and toggles, JavaScript syntax additions including TypeScript integration and pipe operators, essential APIs for cookies and identity, CSS improvements, browser engine debates, and future AI integration possibilities for local model access.

Key Questions Answered

•Customizable Select Element: The web platform now provides a customizable select element allowing full CSS control while maintaining accessibility and keyboard navigation without JavaScript dependencies. This primitive enables developers to style dropdowns completely, with combo box and multi-select variants currently in development, eliminating the need for heavy third-party component libraries for basic UI patterns.
•Cookie Consent API Necessity: The web desperately needs standardized browser APIs for cookie consent management to replace the current mess of poorly coded banners with dark patterns. A native consent API would store user preferences directly in the browser, eliminating repetitive popups across sites. Sentry exemplifies best practices by removing all tracking cookies from their website, requiring consent banners only for embedded content like YouTube videos.
•TypeScript Native Integration: TypeScript has become the de facto standard for JavaScript development, with proposals for types-as-comments allowing browsers to ignore type annotations rather than execute them. Node already supports running TypeScript files natively without transpilation. The browser vendors are taking time to evaluate the approach rather than rushing implementation, learning from past mistakes like premature jQuery standardization attempts.
•Local AI Model Access: Future browser APIs should enable access to device-native AI models for private, free inference while allowing developers to swap in custom models or external APIs. This approach would enable instant natural language processing for tasks like parsing date inputs, validating postal codes, and fixing common form errors without sending data externally or incurring API costs per request.
•Reactive Templates as Primitives: Browsers need native reactive templating where variables automatically update DOM elements when changed, eliminating the need for framework overhead in simple applications. Currently developers must either use full frameworks or manually create rerender functions. This primitive would enable lightweight interactive applications without installing React, Vue, or similar libraries for basic state-to-DOM synchronization patterns.

Notable Moment

The hosts reveal that Canadian postal code inputs create validation nightmares because the format alternates between letters and numbers, forcing iOS users to constantly switch keyboards while dealing with inconsistent capitalization and spacing requirements. They argue this exemplifies why local AI models should handle input parsing, automatically understanding any format users enter without rigid validation rules.

Know someone who'd find this useful?