@jiraTicket No JS, it happens on plain HTML/CSS pages, but it is intermittent. I haven't been able to figure out what triggers it.

I've been putting up with it for years.

Even Matt Wulleweg is trying to kill his own brainchild. Let's hope he's gotten a vasectomoy this time—or whatever other medical procedure cures the urge to unleash spaghetti code monsters like WordPress upon the word.

@Grumm Thanks for the suggestion.

@Chewbanacas That would be `100%`. In this case, that means 100% of its parent's height, with some technical caveats as you can see above (a percentage values also means different things to different CSS properties, one of many quirks that makes the exercise of learning CSS a gift that keeps on giving).

@spongessuck I shouldn't have left the `display` property there. It doesn't actually affect anything.

@Chewbanacas I doesn't take very much CSS proficiency to understand the absurdity in that a `max-height: 200px` parent will not contain a `max-height: 100%` child. You might just say "but that's how CSS works", and that's whole point.

Huh? Hacker New's Algolia search page is the first thing that springs to mind when I hear "buggy search bar." I've searched verbatim for comments I know exist, and they're not appearing on HN's Algolia search page, which on top of that is a resource hog.

@lorentz It's showing through from behind because `filter: drop-shadow()` creates a new stacking context.

@kiki Thanks for actually diving into the specific issue.

This was just an MRE demonstrating the odd behavior of column-count in Chrome and Safari (it's implemented better in Firefox). My actual use case was suitable for a float-based workaround since the stacking order wasn't significant.

And you're spot on that flex and grid can't replicate column-count. That was a hard-earned lesson in my case.

@Lensflare The code snippet is literally just a two-column container with tooltips that's blowing apart.