2 ms·
> So, he's saying that SPAs are bad and we should invest in a Chrome-only feature or future feature that might make it through standards? This makes no sense to
by Aldo_MX 6y ago
> So, he's saying that SPAs are bad and we should invest in a Chrome-only feature or future feature that might make it through standards? This makes no sense to me.
That was my own conclusion, at first I thought "whoa, <portal>? never heard about it but looks cool", I proceeded to search for `HTMLPortalElement` and then I got to a W3C page saying "Draft" and I was like "what? a yet to be standardized feature? thanks, but no thanks, I'll might check it back in 2 years".
- OzzyB 6y agoThis presentation is essentially Dev Advocacy, he's describing where we want to go, not necessarily where we are now. I hear you though; I thought this was gonna be another "you don't need React, here's the Vanilla JS that does the same thing" kinda presentation, but was actually intrigued to learn about this <portal> tag. I does seem to address the (main?!) bugbear we have with interactive webpages and the fight between the server and client. Although I am surprised there's little to no support for it right now - thought at least Chrome would. https://caniuse.com/?search=portal https://caniuse.com/?search=portal Edit: Ofc it can be tried out w/ Chrome if Dev Enabled, but it's not user supported at this time.