Link tags: proposal
39
Page Embedded Permission Control (` permission ` element)
This is an interesting proposal for a declarative way of triggering permission dialogs, although it seems to overlap with the work being done on invokers (command and commandfor).
What really disgusts me is to see Google referring to this element as though it’s a done deal. It’s not. It’s a proposal …a proposal that Apple rejects and Mozilla rejects.
Words matter. Call your proposal a proposal, Google.
Update: They fixed it!
CSS Form Control Styling Level 1
This looks like a really interesting proposal for allowing developers more control over styling inputs. Based on the work being done the customisable select element, it starts with a declaration of appearance: base.
There are plenty of non-men in tech to speak at your conference - Stephanie Stimac’s Blog
I’m going to share this with the organisers of that conference I pulled out of recently.
MSEdgeExplainers/WebInstall/explainer_same_domain.md at main · MicrosoftEdge/MSEdgeExplainers
This proposal is exactly what I was asking for!
C’mon browsers, let’s make this happen!
scottjehl/PE: declarative data binding for HTML
This is an interesting idea from Scott—a templating language that doesn’t just replace variables with values, but keeps the original variable names in there too.
Not sure how I feel about using data- attributes for this though; as far as I know, they’re intended to be site-specific, not for cross-site solutions like this.
Invokers (Explainer) | Open UI
This is a really interesting proposal, and I have thoughts.
Preventing too-short final lines of blocks | Clagnut by Richard Rutter
Check out the demo that Rich has put together to go with Amelia’s proposed syntax.
Audio Session API Explainer
Jen pointed me to this proposal, which should help smooth over some of the inconsistencies I documented in iOS when it comes to the Web Audio API.
I’ve preemptively add this bit of feature detection to The Session:
if ('audioSession' in navigator) {
navigator.audioSession.type = "playback";
}
Scope Proposal & Explainer
This detailed proposal from Miriam for scoping CSS is well worth reading—it makes a lot of sense to me.
WICG/shared-element-transitions
I’m very excited about this proposal for animating transitions between web pages!
I’m less excited about doing it for single page apps, but I get why it’s the simplest place to start.
This builds on Jake’s earlier proposal which I always thought was excellent and much needed. I’m not the only one. Chris agrees.
CSS Anchored Positioning
An interesting proposal for defining how one element could be “anchored” to another, and how that positioning could be expressed declaratively instead of having to write a whole load of JavaScript. Melanie’s looking for use cases so share ‘em if you have ‘em.
Personally, I’m not convinced that a new element is needed but I’m open to the suggestion.
Principles of User Privacy (PUP)
This looks like an excellent proposal for agreement around discussing privacy on the web.
The section on user agents resonates with what I wrote recently about not considering Google Chrome a user agent any more:
Its fiduciary duties include:
- Duty of Protection
- Duty of Discretion
- Duty of Honesty
- Duty of Loyalty
Global Privacy Control — Take Control Of Your Privacy
This sounds a lot like Do Not Track …but looking at the spec, the interesting part is the way that this is designed to work in combination with legal frameworks. That’s smart. I don’t think a purely technical solution is workable (as we saw with Do Not Track).
On the origin of cascades
This is a great talk by Hidde, looking at the history and evolution of cascading style sheets. Right up my alley!
Adding Response Metadata to Cache API Explainer by Aaron Gustafson and Jungkee Song
This is a great proposal that would make the Cache API even more powerful by adding metadata to cached items, like when it was cached, how big it is, and how many times it’s been retrieved.
[css-grid-2] Masonry layout · Issue #4650 · w3c/csswg-drafts
This is an interesting looking proposal for CSS grid to be ever so slightly extended to enable Masonry-style auto placement—something’s that tantalisingly close right now, but still requires some JavaScript to do calculations.
samuelgoto/sms-receiver: phone number verification
An interesting proposal to allow websites to detect certain SMS messages. The UX implications are fascinating.
Limiting JavaScript? - TimKadlec.com
Following on from that proposal for a browser feature that I linked to yesterday, Tim thinks through all the permutations and possibilities of user agents allowing users to throttle resources:
If a limit does get enforced (it’s important to remember this is still a big if right now), as long as it’s handled with care I can see it being an excellent thing for the web that prioritizes users, while still giving developers the ability to take control of the situation themselves.