Archive: October 22nd, 2020

Replying to a tweet from @jaffathecake

Yeah, that’s fair—if I had a time machine, I’d love to go back and make cookies same-origin only.

And JavaScript!

Replying to a tweet from @jaffathecake

Yeah …spicy!

Replying to a tweet from @brianleroux

It’s that emphasis on “between origins” that gets me (though I understand the security concerns, of course). Jake’s original proposal seemed more focused on same-origin page-level transitions …which is most single page apps today.

Replying to a tweet from @jaffathecake

You’re right. I don’t have any in-depth knowledge here. I was trying to describe a proposal being incubated. I used an example. It was a bad example, I guess.

From now on I’ll just describe portals as “spicy iframes” and leave it at that.

Replying to a tweet from @jaffathecake

Jake, I’m not saying that if a technology is useful for AMP then it must be bad—see rel=”prerender”, as you say.

I was honestly, genuinely trying to give an example of where portals could be used based on the description in the explainer.

Replying to a tweet from @jaffathecake

Note that I didn’t say that portals came from AMP; I said they would help the AMP use case.

But I think I must be misunderstanding portals because it sounds to me like it would work great for the AMP top stories carousel.

Replying to a tweet from @jaffathecake

Apologies. I thought the use-case sounded a lot like AMP’s top stories:

…show another page as an inset, and then activate it to perform a seamless transition to a new state, where the formerly-inset page becomes the top-level document.

Google reCAPTCHAs that will help power their new border wall contract:

“Please select all the squares containing children we’re going to separate from their families and put in cages.”

Replying to a tweet from @jaffathecake

Don’t get me wrong: it would be great if portals led to navigation transitions, but right now it looks like the focus is more on “like making an iframe go full page” e.g. an item in a news carousel on a search engine.

Replying to a tweet from @jaffathecake

My description of portals was genuine. I gave a use case (AMP) and a comparison (iframes). I didn’t pass any judgement (although I can see how just mentioning AMP implies ickiness by association).

Replying to a tweet from @paulrobertlloyd

Portals are a proposal from Google that would help their AMP use case (it would allow a web page to be pre-rendered, kind of like an iframe).

Most single page apps are just giant carousels.

Their bucketloads of JavaScript wouldn’t be needed if navigation transitions were available in browsers:

(not portals)

Accessibility Support

A very handy community project that documents support for ARIA and native HTML accessibility features in screen readers and browsers.