I could barely notice the sneaked-in thumbnail in 4:10. Can't believe how stealth the editor was. Jokes aside, this API seems pretty cool. Not something you will use everyday, but something you'll be glad exists when you do need it.
people are saying it is the better twitter but it is really just twitter with a smaller following, once it becomes big enough it'll just be the same old twitter we all hated
@@javierflores09it's smaller because all the nazis stayed on twitter. most people i follow have moved over at this point, and there's increasingly more people deleting their twitter accounts entirely
@javierflores09 not true at all. It's decentralized and built with algorithm that you can control (based on your likes, not your scrolling activity). Additionally, the community is much more positive and outspoken against propaganda, and the algorithm doesn't punish you for content or links. (X's algorithm has been shown to show posts less if they contain a link to another page, or if they mention bluesky for example). This is bad because it means posts with real references aren't promoted on the app and fake news is everywhere. Also if you want to point your following to let's say an app you made or your new business, good luck because X's algorithm won't show it to many people.
Thats neat, i had some really weird workaround for this before... for example not reparent it but move the position and calculate the absolute position. Horrible hack, but it looks good enough
I bet it doesn't change current behavior but why would you call input.remove() at 6:55? An element can only have one parent so appendChild itself should reparent an element without having to call remove before. Intuitively, this should already have the state preserving behavior, though if appendChild implies a remove from the DOM and a subsequent add to the parent child list ... yeah this can get very confusing.
Wooooo that API is going to be huge for WebContainer and its previews. For TutorialKit which uses Astro we had to use a fork of Astro temporarily exactly for that reason. And for the previews we have them absolutely positioned to make sure their state is not lost. Thanks for sharing this! ❤
Please tackle accessibility proactively and don't just rely on customer feedback. Having a usable web, shouldn't require you to hit up devs all the time. Also good luck finding contact info if the site isn't accessible.
Never said you shouldn't be proactive! If you took that message from what I said here, you are part of why so many people get annoyed by accessibility advocates
@@t3dotgg I don't mind the example you showed being for React. I guess I was just excited to see a video about a cool new browser API and didn't get what I expected
You can swap out React for any frontend framework here. The essence of what he's telling remains the same, without this API you have to keep the state of the nodes reactive (even stuff you may not necessarily need to be reactive) so a frontend framework can completely recreate this branch of the DOM elsewhere and make it appear as if it moved, Theos example was a good one in showcasing the benefit imo, this seemingly minor addition to the DOM api is actually huge!
Damn, he ran out of sponsors and had to result to default option, adverts for adverts.
Reminds me of "your ads here" posters in the city.
How long until we get a moveAfter() ?
So is no one going to talk about the colors are actually orange and green not red and blue??
I could barely notice the sneaked-in thumbnail in 4:10. Can't believe how stealth the editor was.
Jokes aside, this API seems pretty cool. Not something you will use everyday, but something you'll be glad exists when you do need it.
Oh, like GlobalKey in Flutter! Or like normal keys if the hierarchy doesn't change.
Sorry if this is off topic, but I haven't moved to bsky yet, and I'm asking if I should?
Yes, is the answer
people are saying it is the better twitter but it is really just twitter with a smaller following, once it becomes big enough it'll just be the same old twitter we all hated
@@javierflores09 that's not true at all due to its architecture
@@javierflores09it's smaller because all the nazis stayed on twitter. most people i follow have moved over at this point, and there's increasingly more people deleting their twitter accounts entirely
@javierflores09 not true at all. It's decentralized and built with algorithm that you can control (based on your likes, not your scrolling activity). Additionally, the community is much more positive and outspoken against propaganda, and the algorithm doesn't punish you for content or links. (X's algorithm has been shown to show posts less if they contain a link to another page, or if they mention bluesky for example). This is bad because it means posts with real references aren't promoted on the app and fake news is everywhere. Also if you want to point your following to let's say an app you made or your new business, good luck because X's algorithm won't show it to many people.
Thank you for covering web platform tech, do more!
Did you create the twitch portal stuff yourself? I thought you mentioned that you used react-reverse-portal
Thats neat, i had some really weird workaround for this before... for example not reparent it but move the position and calculate the absolute position.
Horrible hack, but it looks good enough
I will do something like this when asked to & only when asked, but will remember it at that time. Extremely since it is not in browsers yet.
I bet it doesn't change current behavior but why would you call input.remove() at 6:55? An element can only have one parent so appendChild itself should reparent an element without having to call remove before. Intuitively, this should already have the state preserving behavior, though if appendChild implies a remove from the DOM and a subsequent add to the parent child list ... yeah this can get very confusing.
but it doesn't, state is not preserved, video is paused.
Wooooo that API is going to be huge for WebContainer and its previews.
For TutorialKit which uses Astro we had to use a fork of Astro temporarily exactly for that reason. And for the previews we have them absolutely positioned to make sure their state is not lost.
Thanks for sharing this! ❤
I swear this is already a thing with JQuery no? Or am I trippin...
By separating state from rendering this is moot. I've been able to do this for years without new APIs.
I love the dialog element. This is awesome too.
Why not prependChild?
This is pretty cool and looks like it will fix a bunch of annoying behavior in frameworks. Also the flag is already in stable chrome.
Why only "before"? Where is after?
Will this support CSS transition?
Me moving the mute button for the autoplay video into accordions when the mouse comes to close
Me muting entire browser tab
Safari can't createWritable().
In on the dot
Wait that's just crazy
react portals the ocky way
“This goes way beyond what we can do with react.”
I find myself saying that a lot.
gdi why'd you have to hit me with that 25 and older
I'm thinking of making a software product just to be advertised in a Theo's video
htmx ftw
Please tackle accessibility proactively and don't just rely on customer feedback. Having a usable web, shouldn't require you to hit up devs all the time. Also good luck finding contact info if the site isn't accessible.
Never said you shouldn't be proactive! If you took that message from what I said here, you are part of why so many people get annoyed by accessibility advocates
What does this have to do with React?? Man, React people always talk like everyone is using it..
Over 50% of frontend jobs are in React my man. Not everyone, but it's a very relevant example when new APIs are released.
@@t3dotgg I don't mind the example you showed being for React. I guess I was just excited to see a video about a cool new browser API and didn't get what I expected
You can swap out React for any frontend framework here. The essence of what he's telling remains the same, without this API you have to keep the state of the nodes reactive (even stuff you may not necessarily need to be reactive) so a frontend framework can completely recreate this branch of the DOM elsewhere and make it appear as if it moved, Theos example was a good one in showcasing the benefit imo, this seemingly minor addition to the DOM api is actually huge!
19% of react devs go to primeagen to learn about react😂
if the video was muted why i can heard it in my head?
also, this new feature is sweet
I've heard you say you are color blind and you proved it calling that color blue instead of green haha
This is so cool
E
You're doing too much at this point
third