Comments on: The Weird Parts of position: sticky; https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/ Helping Your Journey to Senior Developer Wed, 07 Jan 2026 03:13:35 +0000 hourly 1 https://wordpress.org/?v=6.9 By: John30013 https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-52639 Wed, 07 Jan 2026 03:13:35 +0000 https://frontendmasters.com/blog/?p=7640#comment-52639 I can sort of see the point that the anti-TW/JSX commenters are making; however, the actual problems the article is addressing, and the solutions to those problems, are fully described in the text of the article. The JSX and TW code are purely there to create the visual examples. You don’t need the example code to apply the solutions to your own instances of the issues this article confronts.

]]> By: William https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-50524 Wed, 17 Dec 2025 20:21:49 +0000 https://frontendmasters.com/blog/?p=7640#comment-50524 Solved my problem with issue #2 that you identified – thanks!!

]]> By: George Madrid https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-48740 Tue, 02 Dec 2025 22:54:11 +0000 https://frontendmasters.com/blog/?p=7640#comment-48740 This was a helpful article. Helped me to understand that our contract programmer really didn’t understand what they were doing when they tried to use ‘sticky.’ 🙂

Feel free to use JSX, React, Typescript, etc. These technologies are baseline in today’s web dev toolbox.

]]> By: Émilie https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-48496 Sun, 30 Nov 2025 16:39:47 +0000 https://frontendmasters.com/blog/?p=7640#comment-48496 In reply to Michael.

I couldn’t agree with you more there. It’s a bummer to see Tailwind here.

]]> By: Jake https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-47236 Tue, 18 Nov 2025 14:15:56 +0000 https://frontendmasters.com/blog/?p=7640#comment-47236 I found this very helpful, thank you.

]]> By: yinhx https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-47102 Mon, 17 Nov 2025 03:05:51 +0000 https://frontendmasters.com/blog/?p=7640#comment-47102 I don’t use Tailwind, but I was able to understand this example by inspecting the CSS in DevTool. It’s not really a big deal.

]]> By: Derk-Jan Karrenbeld https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-47091 Sun, 16 Nov 2025 22:53:08 +0000 https://frontendmasters.com/blog/?p=7640#comment-47091 In reply to Adam Rackis.

My work brings me to many companies and I can promise (and probably even show privately) that there are many many many (web!) developers who have never seen, heard of, or used JSX or Tailwind.

Your world and my world are likely more aligned in terms of what we are exposed to than me and those developers, and there is nothing wrong with that, but please do not assume things like this. It’s not helping anyone.

A CSS tutorial without any CSS included is the bigger issue I have. The styles could have been inlined in a style tag. Using tailwind as a default is a big miss imo. Including the tailwind utilities could have been a cool feature though.

]]> By: Michael https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-47030 Sun, 16 Nov 2025 11:08:38 +0000 https://frontendmasters.com/blog/?p=7640#comment-47030 Also funny how this turorial is labelled CSS and there’s not a single line of CSS in it.

]]> By: Michael https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-47028 Sun, 16 Nov 2025 10:59:00 +0000 https://frontendmasters.com/blog/?p=7640#comment-47028 In reply to Adam Rackis.

Just suppose I don’t have TW installed in my development stack. And I would want to reproduce your example in my own stack?! Should I just dive into TW docs to see what all that stuff on the divs mean?
How is that helpfull?

]]> By: Adam Rackis https://frontendmasters.com/blog/the-weird-parts-of-position-sticky/#comment-46970 Sat, 15 Nov 2025 21:16:24 +0000 https://frontendmasters.com/blog/?p=7640#comment-46970 [Author Comment]

I’m a little surprised by the pushback to Tailwind (and JSX).

The JSX I never had strong opinions on. But Tailwind was a deliberate choice, for the simple reason that I wanted readers to be able to see everything in one place, without needing to bounce between an html, and css flie.

I felt the tradeoff of seeing

self-start

rather than

align-self: flex-start

to be worthwhile if it allowed the reader to see everything in one place.

]]>