Brian Kardell: All right. Hi. So I'm Brian Kardell. I'm a developer advocate at Igalia.
Eric Meyer: And I'm Eric Meyer, also a developer advocate at Igalia. And it's 2026.
Brian Kardell: It is 2026. We made it.
Eric Meyer: Yeah.
Brian Kardell: I guess there's a question if we'll make it to 2027 now.
Eric Meyer: No, no.
Brian Kardell: We started the year and we did a lot of looking back at the year of 2025. And I don't know, somewhere along the way, I just thought, what if we look forward? Are there actually things to be interested and excited about? What are they? So we thought that sounds like maybe an interesting show to talk about some of that stuff.
Eric Meyer: Let's do that stuff.
Brian Kardell: It would be nice to have some, let's look forward in a positive way sort of content.
Eric Meyer: I cannot disagree.
Brian Kardell: So Eric, you got anything that you're looking forward to?
Eric Meyer: Oh, I have things. Anchor positioning is a big one for me in CSS. It's landed in all the browsers. I believe as we record this, I think last week it landed in Firefox stable. So yeah, anchor positioning, you can do lots of really cool stuff. I've been a huge fan of side notes for years and years and years rather than footnotes or end-notes. Those have their places, don't get me wrong, but I just really like side notes for a lot of things where you can just off to one side of the main content say here's what this is referring to. So I'm already doing that a little bit on my personal blog meyerweb.com. I have side notes set up and they should be working in all the browsers now. I mean, I of course over-engineered mine with a custom element and some JavaScript, but not much. And at some point I'll probably also have just plain side notes. But anyway, you can do way more than side notes. You can do tool tips and pop-ups, besides the pop-up element or whatever we're calling it. And you can connect things together visually with a little bit of decoration using anchor positioning. I actually did that. I had an article about that or a post about that. It's been a while now, but I did it for I think wpewebkit.org, just to have a line go from the nav bar link representing the section of the site you're in and there's a little dotted line, go down and then go over and connect to other parts of the design in order to just visually convey hey, this is where you are. Stuff like that could be made a whole lot easier with anchor positioning or is made a whole lot easier with anchor positioning. Yeah, I'm really kind of excited. I think we're quickly going to run into people saying, 'Oh, I wanted to do this thing and anchor positioning doesn't quite get there.' But same thing happened with Flexbox and Grid and every other advancement in CSS really is that people immediately push out to the limits of what the new technology can do and that informs the next revision of what the technology can do. Anchor positioning level two will almost certainly incorporate the working group, seeing what people do with it and people writing blog posts saying, 'Oh, anchor positioning is so cool, but I tried to do this one thing and it didn't work.' And I really think it should have because it just seems so obvious. And sometimes the working group looks at this and says, 'Yeah, that does seem obvious. Let's figure out how we can do that.' So yeah, if you are people listening, try out anchor positioning, give a shot at using it in a progressively enhancing way. And if you have ideas that don't work out, certainly I'll write about it, post about it, blog about it, social media about it saying, 'I tried to do thing, thing did not work.' And you might hear back from people saying, 'Oh, well, here's how you do thing.' Or you might hear, 'Oh yeah, you can't do that because whatever reason.' And then maybe that leads to in the next version of anchor positioning, being able to do that. How about you?
Brian Kardell: Yeah, that's a good example of ... I'm trying to think how to arrange these because I have a list here of some of my own things too. And it's a good example of stuff that is basically across the finish line and it's just like, hey, it'll be really exciting to be able to use it after it's been there developing for a really long time. So anchor positioning, I think the first time that I discussed that in a standards context was in, I want to say 2019, 2020, something like that in Open UI. There already had been a lot of kind of thought into that. And then it got eventually taken up by CS's working group and then it made a bunch of progress. And then as often happens, like opinions happened as it was going through and sort of like whose got time to edit and it changed a bunch. I think it's still great. I'm looking forward to just being able to use it. I guess another one like that is the details element. You have now like Hidden Until Found and all the stuff that, the improvements that have been made on a details element. I think that was all done as part of Interop this year, if I'm not wrong.
Eric Meyer: I think so.
Brian Kardell: And yeah, I just look forward to not having to worry about any of that stuff. It's one of those things where you're grateful to be at that point finally, whereas there's a whole bunch of other things that I'm excited about that are like, they're probably still like maybe really far off in some cases. Some of them aren't even standards related. They're just, I'm looking forward. I want to get that Steam Cube that we talked about a couple of weeks that Igalia worked on.
Eric Meyer: The Steam Cube, the Steam Frame, which one-
Brian Kardell: I think I want the Gabe Cube. Is that-
Eric Meyer: The Gabe Cube, yeah.
Brian Kardell: Yeah. Yeah. I think I want that because I don't have like a gaming PC. I have a PS4 and I mean, I bought it 10 years ago or whatever and I still play it all the time. But there's a bunch of games that my kids play that I can't play with them because they're-
Eric Meyer: They're Windows and yeah.
Brian Kardell: Yeah.
Eric Meyer: Yeah. I mean, I enjoy playing video games from time to time and having a Gabe Cube would be kind of fun because I'm a Mac guy, so like 90% of the Steam library isn't accessible to me. And with the Gabe Cube, it would become accessible to me. The downside of course is that it might suck up a whole lot of my time, but I plan for retirement, have a little Gabe Cube ready for me.
Brian Kardell: Yeah. I guess Temporal is sort of almost in that same kind of vein, right? It's-
Eric Meyer: It's getting real close.
Brian Kardell: It's getting real close. Yeah.
Eric Meyer: It's been in Firefox, at least the nightly builds for a while now, and I believe that it's public now. The Chrome implementation came along later, but is coming along. And Igalia has actually started landing fixes in JavaScript Core, which is the JavaScript engine for WebKit. So hopefully it will come soon to like Safari Technology Preview at least. And I guess it is available, I think in Safari Technology Preview, but you have to use a runtime flag to enable it at the current state that it's in. Yeah. We were just talking with Tim Chevalier, who works for Igalia and has done most of that implementation and I guess it's a very large implementation. So it's in a lot of sort of modular patches and many of them have landed, but there are still more to land and landing requires the whole feedback process of anyone who accepts external patches. In this case, it's Apple, but we go through the same thing with Google or Mozilla. If we have patches, then they got to review it internally. They got to run it against their tests if they have any feedback, et cetera, et cetera, et cetera. So it's not there yet, but it's getting real close. So yeah, fingers crossed that by the end of this year, that will be in all of this table releases, full implementations, and we're just down to the place of, oh, there's this weird bug in whatever browser's implementation and it just needs to get fixed.
Brian Kardell: There's all kind of fun things on there. We did a show ... I don't know, were you here yet when we did that show on Temporal? We thought it was coming actually a while ago.
Eric Meyer: A while ago, yeah. I don't remember if that was me or not.
Brian Kardell: Yeah. So we had several guests on that, but it was a good show. They talk, but there's a lot of talk about those kind of complicated examples that you don't even think about. So it's not just years and days. It's not like you just say, 'Well, there's this many days in a year. You also have to deal with leap years and you have to do with calendar anomalies and you need to deal with like, oh, but this is the way that daylight savings time works in this place versus this place.' And it gets really, really complicated.
Eric Meyer: Yeah. Temporal just makes all that magically go away.
Brian Kardell: Yeah, we hope.
Eric Meyer: Well.
Brian Kardell: So yeah, those are some things that we're excited about. I'm also excited about appearance base. Do you know about appearance base?
Eric Meyer: Tell me more.
Brian Kardell: Yeah. So one of the things that is nice and also frustrating about HTML is that you can lean on controls. So you can just say, give me a select, for example.
Eric Meyer: Oh, so like form inputs and stuff?
Brian Kardell: Yeah, for form inputs. So you can have these interactive elements that a complex widget of some kind and you don't need to worry about a lot. You just declaratively say, 'I want this.' And then it's up to the operating system how that gets displayed and it could be different, right? And so that's like been a selling point for HTML for a long time. That allowed, for example, when you have a select on your mobile device, your mobile device gives you a picker that's more appropriate than it would, than just what you would get size wise on your desktop. It's cool, but sometimes it means we've given almost no ability to style it. And even to the extent where we want to talk about parts that we want to style and we're like, parts, what parts? I don't know.
Eric Meyer: Well, because those form controls, like selects or radio buttons or whatever, in CSS terms are replaced elements. They're like images. You're not supposed to be able to see into that box. It's like, here's a box and a thing gets put there and that's, we can do things around it, but that's it. And obviously that's come up against designers wanting to make the radio buttons have the color that matches the color theme of the site or et cetera.
Brian Kardell: Because the composition of them varies, there are sort of like browser specific pseudo classes in some cases where it's like, oh, well, we exposed the thumb for this control.
Eric Meyer: Or what the separator, if there's a separator, could look like between select entries, like select options.
Brian Kardell: Sure. Yeah.
Eric Meyer: Yeah. And actually, I was just thinking, as we were saying this, in a lot of ways, form elements are a lot like web components. There's like a shadow DOM and you can't look inside, except there have been these little ways to pierce that.
Brian Kardell: Yeah. I mean, in fact, that is part of how the design of shadow dom and custom elements comes about is there's parallels for everything in the platform in the design of custom elements, more or less. So appearance base is like the first time when we lay out pretty specifically like sort of here's the white label version of this control and here are the relevant parts that you can style. And they're the same for all the operating systems. And I think that there are some sort of like cutouts for if you wanted to do like the mobile thing, maybe that still is mobile, but yeah, if you have the control, you can style it and it's not going to be different on Mac than it is on Windows or whatever. You're not going to be like, this part exists in this and not in another one. What's exciting to me is that this has always been sort of like completely off the table as a answer. And it's another one of those things that's taken a really long time. The first conversations I had around this were also in 2019 with Greg Whitworth at Open UI and he was like, 'If we can do this, then we can do a lot of things. We can make a lot more things stylable. We can make a lot more things more predictable.' And yeah, anyway, it's good to see some attempt here because I think we haven't had a real attempt at answering some of these questions before and I'm really pleased to see the people who are working on it and the progress that it's making. It's not like there's nobody who's like, 'We just can't do this.' So it'd be great to see what happens with all this. I'm excited because it's a fundamentally new thing. It could be amazing or maybe not.
Eric Meyer: Yeah. Well, I still feel that form elements should be operating system consistent so that it doesn't matter what browser you're using, users immediately recognize a thing.
Brian Kardell: But I think your position is even more strict than that. You would almost like them to be less stylable, right?
Eric Meyer: Yeah, pretty much.
Brian Kardell: Yeah. What else? Do you have anything else on your list that-
Eric Meyer: I mean, those are kind of the big ones that we've covered so far for me. There are other things I'm sure that I'd be like, oh, cool. And there's stuff that's been discussed, for example, in the CSS working group that is cool, but it's not shipping right now. So this stuff around line heights and box trimming, I think those are nice. Again, not exactly going to set the world on fire. The web would not be hugely restricted if those never landed. We've worked with them so far, but having them land to be able to say that for this element, like for this div, margin should not stick out of the top and bottom of the div, they should be trimmed off. Sure, that's kind of cool. And line clamp and initial letter and things like that, things that lead to more typographical richness and sort of more typographical consistency so that rather than having things where things just look a little off because we're using programmatic rules rather than somebody who is literally laying out pages lead block by lead block and able to say, okay, we're going to shave this space out because it just looks better or we're going to add a little more space here because that helps it conform to the line rhythm. That sort of thing. Those are being landed in some cases, discussed in other cases, moved forward. Just that whole bucket of more typographical subtlety and richness I think is pretty cool. I like that sort of thing. Text fitting is another one that's in there, the idea of being able to say, well, I want the font size of this text to be whatever will make it exactly fill out the inline space that it has, like for headlines. That's been a thing that people have written JavaScript to do and that Roma Karov has written completely mad CSS to try to get real close to. And I honestly think that both of those things together, the working group is now going to just be able to sort of say, all right, here's how it would be done. What's the property value combination or combinations that we want to make it happen natively? So those are at least some of mine.
Brian Kardell: You know what I am excited about is web speech, which might sound funny because it's another one that dates back really, really far when it got started, but it took a long time before it got implemented everywhere and it's always been wonky and bad. And I've been trying since I think 2017 to get the ball rolling on that again because there's just a lot of things you should be able to do with it that people are doing with similar technologies, but you would like them to be able to use web speech. Now it is getting some attention and movement and they just recently added a way to do like when you're listening for transcription, how to add sort of like contextual biasing so that if you have words that maybe sound alike, you can bias them toward hearing the right word. So this is also useful when you get to like names and like proper nouns and things that it's like unlikely to hear unless you give it some hints about like, these are the things that I want you to hear. So if you had, for example, a tech podcast, maybe you want to like load that with like a bunch of terminology and say, 'These are words you're likely to hear,' and make sure that these are the ones that you're hearing, not something that might sound like it. Now there's a bunch of energy to maybe completely fully redesign part of the APIs around how to speak and make it promise-based. And yeah, I think that's just really exciting.
Eric Meyer: Yeah. And I mean, for those who like to have speech happen, like this is for the turning text into speech, right?
Brian Kardell: That is, but for both, like there's a lot of energy to next take up the how to speak as opposed to how to transcribe, maybe a full redesign of that.
Eric Meyer: So wait, how to speak versus how to transcribe?
Brian Kardell: Right. How to hear versus how to speak.
Eric Meyer: Okay. I see. Yeah. It's interesting too, I saw one of the other things on your list was spell checking and like where those overlap or don't overlap.
Brian Kardell: Yeah. Yeah. It's those three things. And then there's also a bunch of proposals around like machine learning that also have to do with sort of like ... Well, all of these have to do with something similar in that it's like, let's say you have a site that is dedicated toward Pokemon, right? That's the example used in a bunch of explainers and things because Pokemon has all kinds of like made up words that sound like other words. And if you have them typed in, you say, 'Spell check this,' your dictionary is not going to contain Charizard. You know what I mean?
Eric Meyer: Right.
Brian Kardell: But maybe it will auto suggest a few things that you might mean. It'll mark them with squigglies as those are wrong. Maybe if you read the page out loud, if you had to read the page out loud, it would, I don't know what it would do. And if you tried to speak as speech input, like have Charizard attack, blah, blah, blah, right? It's unlikely to hear that. So in all of these cases, you need to provide some kind of context that is domain specific. And so I'm working with our colleagues, Ziran and Steven on spell check dictionary and that's the point is very similar. You have your operating system might provide a dictionary, your browser might provide a dictionary. When you click to add things, you can add them to your dictionary. Some browsers let you go and like add words manually to a dictionary like through some interface. But what happens when you go to a site and the site is about Pokemon and you don't have the Pokemon in your dictionaries. The site is like, no, don't worry, I'll provide you with the dictionaries. So there's a lot of question about like how to design those features. This is like really interesting and fun to think about all of them at once, but also it's frustrating because some of them are already shipping and there's like pressure to ship and also questions about how important is it for them to share stuff. Yeah. Anyway, it's exciting to be involved in and working on in terms of sort of both of those things. So I'm recently on the new web audio working group for the speech stuff and also working on the spell-check dictionary. So we'll see. We'll see.
Eric Meyer: Yeah. What else you got?
Brian Kardell: I'm keen on maybe them restarting the web monetization work community group. And yeah, I don't know how to put this in the right way. Yeah, this is a spec that is known by web monetization and it is basically the thing that used to be with coil. And I think there are a lot of open questions and there are a lot of open challenges. I don't know how much that needs to be reshaped or what needs to take place, but I know that we don't get there without it getting some energy into it and people interested in discussing. So I'm keen for there to be some interest and energy into discussing and trying and seeing where it goes.
Eric Meyer: Yeah. I mean, it's always been the thing that feels like it's sort of missing from the platform is the ability to monetize without going to advertising.
Brian Kardell: Yeah. Yeah. I don't know.
Eric Meyer: Yeah. I mean, nobody does, that's the problem, but it would be nice if we could finally figure it out. I mean, it took a quarter-century to figure out has in CSS.
Brian Kardell: And it's a little bit harder than has, maybe.
Eric Meyer: It might be a little bit, yeah.
Brian Kardell: Yeah. I mean, I don't know if it is, honestly. We talked about that offer wall, I think, a while back. That's a similar idea in a way. And I believe that the web monetization people are looking at how they could even plug into that. So maybe there are a lot of things coalescing toward, at least again, the energy and excitement and not just this is stuck. To me, this is ... I guess maybe this is sort of like the point of the show for me is like, for me, a lot of things that are hopeful and interesting are like, these are just unstuck and that's exciting to me because a lot of them get stuck. So almost all of the things that we talked about started six, seven years ago or more. You can add to this MathML, MathML getting more interoperable. We're doing a bunch of stuff with the Sovereign Tech Fund to fund math interoperability this year, and that's huge. Part of that ends up resolving differences in link types between MathML and SVG and HTML. And that's all just because it's like somebody's giving some funding to solve those problems and they're not just stuck.
Eric Meyer: So what are the link types?
Brian Kardell: So MathML and SPG both have this concept of links, but they're just like, you can put an HRF on anything. And a lot of people think that sounds good on the surface. I mean, it definitely makes some sense, but there are a lot of things that depend on your ability to sanitize HML and to then plug in all the things that we do with Link. Do you have a target attribute like is that work? Do you have like no index, no follow, you know what I mean? All those other Things that go into linking, none of that was really specified. And SVGs is different in a way, in weird ways than HTML links, and math links just sort of never were specified well at all. So getting them all working and all the same and all as safe as one another and interoperable and also just shaped the same way is small but really important things. I heard Anne van Kestren in 2012 or 2014, 2014 I think, give a talk at the first extensible web summit that we had. And he gave an intro talk and he said, HTML5 is way, it's exciting. Yay. But a lot of the stuff that made it survive and made it be good and made it successful were the Parser stuff. And that was the first thing that had to be done is this Parser stuff. And it was painful and boring and seems like not the most important, but in the end it is really, really important. And so it's just awesome when we can get that stuff done because it has big out-sized impacts.
Eric Meyer: Yeah, that makes sense.
Brian Kardell: I am also looking forward to maybe a WP based Android browser, a WebView anyway, and then a mini browser that we can play with that I would love to see grow into something else. I mean, that's just me looking forward hopefully, I guess. I don't know that it will ever happen, but I think it's very interesting.
Eric Meyer: Oh, there's one that I forgot about until just now. Heading levels.
Brian Kardell: Right. Yes. Heading levels.
Eric Meyer: So that's Keith Amus is driving that from Firefox, right.
Brian Kardell: Mm-hmm.
Eric Meyer: And yeah, he's been pushing this forward to get it so you can basically say, here's how much you should offset all of the heading levels in this sub-tree of the DOM very easily, and I dig it.
Brian Kardell: Yeah, we did a show about it. We had him on, Keith Cirkel. Keith Amos is his handle everywhere. If you're listening audibly, that's his handle everywhere. So yeah, we can link up the show, but literally the oldest problem on the web.
Eric Meyer: Yeah, pretty much. Which the document outline algorithm was supposed to solve and then failed to because the algorithm failed. Well, implementation of the document outline algorithm never happened. But yeah, I think, was it you? I think it was you who asked people like, 'What is the thing that you would fix?'
Brian Kardell: Yeah.
Eric Meyer: Oh no, no. Sorry. Well, yeah, you probably got it there, but then I also, not too long ago, put up a social media post where I was basically like my hot take on web technology that gets me surrounded by a bunch of people with swords is this. And what's yours? And I did get a bunch of replies and one of them was we shouldn't have heading levels. There should just be each elements and the browser should just figure out from the structure what their level should be. I was like, 'yep, pour one out for the document outline algorithm, because that was kind of the deal. So yeah, this is not that. This is a halfway step, I guess, or it's a middle ground where you can just say, hey, in here, add two to every heading level. So H1s become H3s and H2s become H4s or fives. H1s become H4s, whatever. Yeah, I think I did math wrong, but yeah, which is really useful for a lot of things. If you know that content is going to be viewed in multiple contexts and usually if it's going to get inserted into other contexts where heading levels already exist, then being able to just offset them is super keen. But yeah, people can go back and listen to the episode that we did for more details. But yeah, that looks like it's moving forward, so I would love to see that start landing this year. That would be great.
Brian Kardell: You know, one of the things about the web that's just phenomenally interesting, I think you were talking about, you asked a question on social media about what's the hot take that gets you ... I also did a thing on social media a while back that was like, what's something that you really thought that you wanted so much, and then we got it and you're like, hmm, I don't actually use that very much? I wonder actually how this will play out in the long run because it is literally the oldest problem, but because it's the oldest problem, it means that we have more or less solved it in other ways. And so now the question is, will people actually adjust and how much and what are the reasons to do it? So will you change your blog, do you think?
Eric Meyer: I will.
Brian Kardell: You will?
Eric Meyer: Yeah. And I do have this problem. Well, yes, I will change my blog in a few ways. I think this is going to be one of the many, many, many, many features of the web platform. And by that, I mean things that are in HTML, things that are in CSS, things that are in JavaScript, where there are a whole lot of things that you don't use very often, but when you need them, you're really glad they're there. The paragraph tag is not one of them, like you use the paragraph or the div tag, right? You use the development everywhere, basically. You use the CSS color property pretty much every time you write a full style sheet, but CSS has stuff that I rarely use. And in fact, I use rarely enough that when I do use it, I have to go look up the syntax because I can't remember. I'm like, okay, there's this property that does this thing I think it's called, blah, blah, blah, but I don't remember any of the values. Let me MDN, look it up. There's a lot of that. We're well past, I feel like, the point of doing things, adding things that will become absolutely core to everyday work. Whereas anchor positioning is an excellent example. I think so many cool things can be done with it, but is it needed all the time? No, it's not. Never will be, I don't think. I don't think it'll ever be needed all the time. It's just you miss it when it's not there and once it's there, it'll be a, God, I'm really glad we have this. This is so cool. And I think things like the heading level offset is very much that. A lot of websites will have no need for it. And a lot of websites that do have need for it will miss that it's available and so won't use it for a while. But there will be situations like on Meyerweb, the title of a blog post is supposed to be an H1 on a page that shows that individual blog post, but it should be an H2 on archive pages. And then I have a little bit of code in WordPress that does that, but I then have to skip heading levels. If I want to put headings in my posts, I usually end up skipping a heading level in some context. And this is why I almost never put heading levels in my blog posts because it's such a pain and I know that in one context or the other, they'll be wrong, like there will be an accessibility problem. So I very rarely use them. And with this, I would feel more free to use them. I mean, not this year probably. I would want to wait a year or two for that sort of thing to become widely available, but ...
Brian Kardell: Yeah, I think it's going to be huge. I don't think this is a thing that we're going to go, hmm, no, in the end, we don't really want that. I think we definitely want it. I think it's going to be huge, but I think it's also one of these things that is going to take a long time to permeate. And why I think it's interesting is because a lot of the success of these, we won't be able to measure for five to 10 years, right?
Eric Meyer: Yeah. Yeah.
Brian Kardell: So I'm not rewriting my blog because I can write headings a different way, probably. But when I do rewrite my blog, I will probably use that. If I write some new site, I'll probably use that. Not probably. I'll definitely use it when it's available. But right now you need a polyfill and the polyfill can't do some of the things that you want it to do. So probably I'll just wait. I'll just wait. And yeah, once it's available, then I write some new content, I will probably use it.
Eric Meyer: That makes sense.
Brian Kardell: I think there are a lot of stuff like this. I mean, Grid is also growing slowly, not because Grid isn't awesome. It's so awesome. Anything that's new that's being written has to use Grid. I can't imagine how you don't use Grid, right? But we actually work on websites that aren't using Grid, and well, there's nothing wrong with the website. So we're not going to invest money into rewriting it to use Grid, just to make it use Grid.
Eric Meyer: Yeah.
Brian Kardell: Yeah.
Eric Meyer: You wait until the redesign for the Grid.
Brian Kardell: Exactly. Exactly.
Eric Meyer: I think that's fair.
Brian Kardell: And the thing is, the web is very stable, so it ages slowly. So when we look at all these statistics about websites and how much things are used and all that, yeah, there's still bias and all that data toward JQuery because it's just still there, still works fine, which is actually the strength of the web.
Eric Meyer: Yep, absolutely.
Brian Kardell: Is that my whole list? Oh, no. When I first came here, I had a lot of questions about embedded systems. I didn't know a lot about them, and I was like, 'Well, so they're kind of like web views.' And it was like, well, some people said yes, some people said no. And then there was also this effort to make these mini apps, which I was like, 'So they're kind of like web views.' People were like, 'Well...' And then there's also all this work on sort of like the Fugu stuff that's like, well, it's sort of like the stuff that you do with electron and stuff like that. And it's like, well, so this year at TPAC, there was a joint meeting that was like a bunch of those interests together and there was like this, hey, this mini-apps thing doesn't really seem to be getting where we wanted to get it and WebViews isn't kind of getting enough of what we want and these other proposals aren't really going somewhere. And there just seemed to be some interest and willingness into getting all those interests together and finding the common ground and trying to find what we could do. And I think that's really huge because basically everything is written with web technology, but lots of it is just not standard to the same extent that the HTP web in the web browser is standardized, but it would be great if more of it could be. So I'm really looking forward to the possibilities that could open up because I would love to learn a extended thing or find a way like the FUGU stuff to give powerful features in a safe way or whatever, so that we'd make it possible to develop lots of that stuff closer to the platform, not rely on frameworks and things like that.
Eric Meyer: Yeah. Okay. I feel like that's a good look ahead.
Brian Kardell: That is a good look ahead.
Eric Meyer: So those of you out there in listener land, let us know on social media or wherever else you want to send feedback, what you're looking forward to in the web platform in 2026.
Brian Kardell: Yeah, probably all kinds of stuff that we didn't even talk about, I would imagine. So look forward to hearing what those are.
Eric Meyer: Yeah.
Brian Kardell: And we didn't cover only one thing from JavaScript.
Eric Meyer: Right. And there's probably way more that we should have been looking at, but yeah.
Brian Kardell: Yeah. Lots of DOM stuff that I know of that we didn't cover either that have to do with like Canvas or like web audio or all kinds of cool stuff. So yeah, there should be rich for the comments. So share your excitement with us and maybe we'll come back and talk about some of those things.
Eric Meyer: Yeah. Yeah. I was just thinking let us know and we could do a follow-up and sort of cover, mailbag as it were.
Brian Kardell: Yeah.
Eric Meyer: Cool. All right. , thanks. Yeah. Thanks, Brian.
Brian Kardell
Eric Meyer