Tailwind broke, but it's not their fault...

[@xLastxTemplarx]

Change the title my man, it's a chrome issue, don't clickbait!

[@ahmadaccino]

tailwind haters going to run wild with this one

[@tacocrunchies]

as they should

[@diadetediotedio6918]

@@tacocrunchies nah, they should not.

[@edwardallenthree]

It continues to baffle me that, after years of demonstrating dramatically increases productivity, reduced CSS size, better looking sites, that people still hate it.

[@krazymeanie]

​@日本語だけを聞くために-n3o cope because people prefer to do this the way they were meant to be done?

[@edwardallenthree]

​@@krazymeanieThe way CSS was meant to be done, with CSS controlling all of your presentation in one document, and your HTML describing only the content in another, is broken. It does not work. It is not a good workflow. You can talk about how it's the way it was meant to be, but the way it was meant to be doesn't work for many organizations.

[@CyberTechBits]

You don't need to click bait. We already watch your content! Don't push us away 😢

[@dissolvesoftware]

Next: Shadcn UI just broke a whole ton of websites

[@jaymr2795]

I mean you literally download the component and put it in your sourcecode, so as long as you don't change it/update the component deliberately, an update shouldn't be able to break it.

[@statuschannel8572]

@@jaymr2795 shadcn uses tailwind so if tailwind breaks shadcn component will break too (but this is a chrome bug, he just click baiting us)

[@jaymr2795]

@ ah, now I get what you meant. True!

[@NickHamilton88]

@@statuschannel8572shadcn also uses radix-ui

[@Simon-ir6mq]

Man, browser bugs can be nasty. Reminds me of when I found out that mouseleave events are not guaranteed to be triggered (even though you exit the element), thus there can be mouseenter without leave. Not sure if it's a bug or just a naming that invites wrong expectations on my side. In any case I feel for the tailwind maintainers for getting caught up in this.

[@ahmadaccino]

i remember a senior dev ripping into me one time early in my career when i used a mouseleave. had no idea

[@mattymerr701]

If you alt tab to another window, move your mouse then alt tab back, there is no way for the browser to really know the mouse left with the way messaging works without weird hacks. So it doesn't surprise me

[@Simon-ir6mq]

@@mattymerr701 I don't mean changing tabs. If you move across a sufficiently complicated dom at the right speed some elements fire mouseenter but not mouseleave. I guess tabs justify why browsers cannot generally guarantee anything with regards to events.

[@adityaanuragi6916]

A disabled button doesn't fire mouse enter but it can fire mouse leave I have no idea why

[@gsgregory2022]

The bigger question is what haven't we realized is broken via this chrome change? It could be that this weird text highlighting in tailwind was the only thing impacted but that seems unlikely.

[@JD-kx4rh]

Many of you haven't had to support IE4 and it shows. This is what being a web dev used to mean.

[@friendofzeus]

Thank god that thats no longer the case and we can focus on actually building shit.

[@Seanmclem]

Kind of a bait headline. Seems like chrome broke a small quality of life feature. Not tailwind straight broke websites.

[@no_the_other_ariksquad]

Please don't name your videos like this...

[@andrisoone]

Theo just broke a TON of websites...

[@mateusvahl5072]

Click bait =(

[@davbrito]

7:25 it's not a pseudo class, it's a pseudo element

[@ramsey2155]

Theo, i like you and your videos. But when you bait people this hard you break my heart

[@Mostafaabobakr7]

Disliked for the clickbait

[@joaocouto90]

so, technically CSS (and chrome interpretation of csss) broke many sites.......

[@MadMikeyB]

Not a tailwind enjoyer but this is a Chrome issue. Not a tailwind issue. Tailwind did nothing wrong, Chrome broke functionality. Please re-title the video to target Chrome and remove clickbait

[@xprowler404x]

14 comments, the algo is more broken then tailwind 💀💀

[@laluneodyssee4404]

Chrome messed up scrollbars that used the firefox standard in 129 too I think

[@jakubczarlinski]

another day of NFSW spam bots on KZbin beating me to "first"

[@deatho0ne587]

This does not break anything, it just does not give feedback for certain things. Yes, not very user-friendly but still.

[@wolfphantom]

:: is a pseudo-element (there are 2 colons, like an opening and closing tag). Whereas, a psuedo-class is a single colon (like a single period for class selection)

[@lessko9]

If only the comment section knew theo is a big tailwind proponent

[@LEDsellers]

I was losing my mind this weekend seeing my RTE library not highlighting text properly and turns out it was chrome…

[@envigraphy]

videos like this are the reason why we still need the thumbs down button on KZbin

[@jakemetz1742]

Where can we find what the styleX creator said about tailwind concerns?

[@DEVDerr]

This title is not-fair for Tailwind :/

[@Kindjie]

This Chrome version also “broke” ‘font-variant-emoji: emoji’ by rendering digits as emojis - it manifests as numbers appearing to ignore formatting to the untrained eye. Took an hour to figure out, and according to the bug ticket, there’s a disagreement on how to interpret the relevant unicode/CSS standards. At least it was a relatively simple workaround. 🤷

[@RobbPage]

so chrome broke a ton of websites, not tailwind...

[@ratsock]

If anything this is more reason to build it into the browser

[@edwardallenthree]

@@ratsock I'm not in favor of building tailwind in a browser, but you're right. All of the arguments presented make a good case for doing it. The reason I am opposed is that I want to continue to see innovation by tailwind.

[@mattymerr701]

​@@edwardallenthree innovation still happens to things that are built-in to the browser? JavaScript, CSS, and HTML are all constantly updating

[@edwardallenthree]

@@mattymerr701 Yes, that is why I have multiple copies of Flanagan's JavaScript The Definitive Guide. Perhaps "innovation" wasn't the right word. Direction. "Direction," is the right word.

[@jacobwwarner]

WordPress world is advocating against Tailwind in favor of "css framework" plugins which are really just graphic UIs to manage CSS classes.

[@darquill]

Theo, I like your content, but please don't clickbait.

[@RadikAlice]

Classic Chrome moment. Internet Explorer didn't stop existing, it was reborn in two different forms. Chrome is the monopoly manipulating the web to suit its whims, Safari is the old clunker holding everybody else back because it has to be supported due to market share. I will die on this hill EDIT: More like, be careful to run Chrome

[@cugansteamid6252]

what browser is he using guys?

[@kriffos]

I think it's Arc browser.

[@KaKi87]

> I'm not gonna revert to a weird patch of a patch That would be easy on Linux thanks to package managers.

[@vaisakh_km]

Recently service now had same issue with edge browser...

[@jian-was-here]

How much did google pay you for this

[@tanglesites]

I prefer to write my own css. Sass + Vite + CSS = no bugs.

[@jason_man]

well, back to using pure css i guess

[@cherubin7th]

I learned about tailwind from you and it was so helpful, it is awesome.

[@DeepTitanic]

He’s sponsored

[@t3dotgg]

...by Tailwind? I've never been paid a cent by them.

[@kasper369]

It's more of the browsers fault than tailwind

[@philadams9254]

More clickbait BS I don't have to watch thanks to DeArrow

[@the.monologue]

the clickbait is unironically so annoying man. just say "funny chrome bug"

[@cooltune]

Well the chromium boys are on a roll lately bothing release after release. I see JS api and CSS behaviour change left and right. The dev tools also started to behave super wonky lately.

[@0xSatyajit]

I faced this issue on twitter amd thought arc broke again 👀

[@devor8251]

Modern SSR React is an improved and reimagined version of PHP. Tailwind is a rethought good old css classes mess on strong steroids. The circle is complete-what’s next on the spiral?

[@tanglesites]

I would have to disagree. Css is kinda amazing all own its own.

Used posthog, like it, so yeah, free ad from me.

[@SimpleTutorialsIndia]

Click bait

[@NeoVirusOfficial]

You clickbait too? :/

[@yannick7049]

Chrome causes bug but it's Tailwind fault? Also very funny so soon after a video about how we should protect Chrome at all cost and makes me wonder if this is a case of just clickbait - although I'd say it isn't clickbait, it is just you lying - or that you just think Chrome can do no wrong...

[@pencilcheck]

chrome bug

[@aditya.khapre]

Tailwind is the shxttiest industry trend that we are forced to follow because "big" companies do so.

[@jeffrbake]

And this is why I prefer Firefox 😊

[@leonardodavinci2856]

and vscode broke apc ui ++

[@A453]

Not an issue because noone should be using chomium browsers in 2024. Chrome was cool in 2008. Modern, standards-compliant web engines like Webkit and Gecko are so much better.

[@StCost]

hello

[@crowlsyong]

oh hi

[@LarsRyeJeppesen]

No they didn't

[@mkrichey1]

Cool video but no like due to clickbait :P

[@UODZU-P]

Ah yes, big tech tuber talking head posts title for people who don't read to just go and be mad at Tailwind on Twitter. Do better

[@dovh49]

Pico CSS FTW!

[@franciscogonzalez1879]

Chrome biased

[@polski003]

I love tailwind

[@WiseWeeabo]

Bruh they can't just remove a css feature.. I hope the government actually makes them sell Chrome, hopefully whoever gets it can make a lot more rational decisions..

[@frosty2912]

Just write CSS, it's easier

[@lessko9]

Plain css with daisyui ? Nope

[@dan_goosewin]

quack

[@AbidKazi-w1k]

Tailololololoololo 😂😂😂😂😂 🤣😂🤣 There are way better css frameworks out there

[@BeeBeeEight]

Even though the title is clickbait, I still think it's good to be aware of being overly dependent on tailwind and its derivatives (shadcn, daisyui etc).

[@trappedcat3615]

I just got wind of this. Glad I'm not at the tail of it. Long live vanilla CSS.

[@statuschannel8572]

think about it tailwind also going to be vanilla css after building. this is a chrome bug labelled as "tailwind"

[@mikahfeldman-stein3470]

Posthog developer experience was one of the worst I've ever dealt with. Implemented it in a production app and it was brutal. Also very slow ingestion of data (they batch data, no real time) making the pace debugging impossibly slow. We ripped it out after a month. Waste of time and money.

[@toifel]

BS slop.. time to unsub from this clownshow

[@RobbPage]

man i am getting so close to unsubscribing from this channel.

[@samhudson1169]

Tailwind is garbage

[@richardhaddadau]

How dare you say it's Tailwind? How could you!? lol. Yeah yeah, calm down people. We all know it's not Tailwind. Watch, enjoy, like, move on.

[@phead2137]

Nothing against tailwind but it’s definitely not standard anything.

[@belkamax05]

I don't like Tailwind, anyways.

[@firesidecode9065]

Wow I’m early

[@crowlsyong]

I'm late

[@meta7gear]

.Tail .wind .is .awful .just .write .some .css .its .not .that .hard

[@woeky]

.monkey .balls .monkey { content: 'bad'; } .balls { content: 'argument'; }

[@Alkaris]

Glad I'm not using Chrome then. Gonna be sticking to Firefox or any other competitor that isn't built on Chrome. I'm tired of _"Yet Another Chromium Browser"_ and whatever dumb and broken changes Google tries to force on the Web Standards.

[@Yoshi-t5xKm]

i love tailwind