Most Humble Ui Designer

Rejecting frontend work? Reasonable. Avoiding backend tasks? Understandable. But the weekend? That's the sacred runtime environment where all my personal processes finally execute without interruption. No standup meetings, no Jira tickets, just me and my neglected side projects that will definitely get finished this time. Definitely.

Ah yes, the classic "unmasking the villain" trope, but with browsers. Turns out your "Chrome replacement" is just Chromium wearing a Telegram logo mask. It's like switching from Coke to Pepsi and calling yourself a health guru. The browser market is just Google in various trench coats at this point. Your privacy settings are basically just suggestions to the algorithm.

Content 57 This likely has to do with the issue addressed here: CSS overflow-x: visible; and overflow-: hidden; causing scrollbar issue In short, when using visible for either overflow-x or overflow-y and something other than visible for the other, the visible value is interpreted as auto. Share Edit Follow edited May 23, 2017 at 10:29 Community Bot 1 01 answered Jun 10, 2013 at 9:02 Sprintstar 8.058 06 39 51 48 is this a bug that browser vendors should fix or spec by W3C? Because it's awful... - ProblemsOfSumit Oct 4, 2013 at 10:17 26 2.5 years later and this bug still exists - Daniel Kobe Apr 16, 2016 at 8:06 FF 52 and this still happens. add one more year... - Sebastianb Jul 31, 2017 at 19:22 5 FF 57, here too - fedetibaldo Nov 30, 2017 at 18:10 19 Guess which issue still exists at the end of 2018... facepalm - Vitalii Romaniv Dec 12, 2018 at 9:54 5 This bug is still haunting my projects - ApplePearPerson May 22, 2019 at 14:18 4 Still a bug.... FF72 can't believe they haven't fixed that one yet! - benitek Feb 2, 2020 at 16:05 26 2020 still the same... - Eduard Fedoruk Mar 30, 2020 at 15:31 24 2021 and this hits harder than covid - Sasa Sijak Jan 14, 2021 at 8:55 13 I'm from the future. It's 2045, the issue still exists - Roudy Tarabay Apr 15, 2021 at 10:10 12 2022 just knocked in and the issue still exists.: - Deepak Yadav Dec 31, 2021 at 19:10 2 This is legit unacceptable! - Ben Racicot Sep 19, 2022 at 14:26 5 10 days till 2023 and still: I lost almost a full day trying to figure out why my CSS does not work as expected... - BlaM Dec 21, 2022 at 16:42 BlaM Glad to still be helping, ten years later :) - Sprintstar Dec 22, 2022 at 16:30 2 The cvcle continues. . - Nicholas Aponte May 3, 2023 at 17:15 2 September 2023 and we still have this behavior - Dayron Gallardo Sep 12, 2023 at 15:42 2 I'm from 2024 and we still have it - Jiren Jan 30 at 16:04

Content Admit web development has become a convoluted mess Build Al to find optimal combination of front and back end frameworks

JavaScript, the DRAMA QUEEN of programming languages! Look at this unholy abomination where an empty array plus 1 becomes "1" (a string!), but suddenly [1] + 1 transforms into "11" because JavaScript decided type coercion was feeling extra spicy today! And then [1,2] + 1 gives us "1,21" because WHY NOT just concatenate everything into a string salad?! JavaScript's type coercion is basically that friend who NEVER follows the plan and just makes up rules as they go. The language equivalent of saying "I'm not chaotic, I'm just quirky!" 💅

The eternal lie we tell ourselves: "It works on my machine!" Left side: Your code running on localhost - a magnificent beast with muscles that could bench press a server rack. Status 200, everything's perfect, and you're basically a coding god. Right side: The same exact code after deployment - a pathetic, malnourished doggo surrounded by CORS errors, cookie sharing issues, and bad requests. Suddenly your beautiful creation is about as functional as a chocolate teapot. The production environment: where developer confidence goes to die and debugging nightmares begin. But hey, at least it worked in development!