Lea Verou • 1/9/2012

What we still can’t do client-side

Read Original

This article examines several significant limitations in modern client-side web development that lack proper specifications or APIs. It discusses the inability to do cross-page templating without JavaScript, the lack of a sane standard for client-side localization, the absence of a screen capture API for DOM elements, and the impossibility of accessing POST parameters or HTTP headers. The author argues these are fundamental gaps that need browser-level solutions.

0 comments
#web standards #web components #Localization
What we still can’t do client-side

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Using Browser Apis In React Practical Guide
Jivbcoop • 2 votes
3
Top picks — 2026 January
Paweł Grzybek • 1 votes
4
In Praise of –dry-run
Henrik Warne • 1 votes
5
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
6
Vibe coding your first iOS app
William Denniss • 1 votes
7
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
8
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes