Why even use grid when you can solve this much easier without it?
How would you do this otherwise?
Full-Bleed Layout Using CSS Grid
61–70 of 277 posts
Re: Full-Bleed Layout Using CSS Grid
#62Slightly OT, but this page has the BEST alternative for a modal newsletter pop-up I’ve ever seen. I have a personal rule that I close the tab as soon as a modal asking for my email pops up. When the cute little figure on the left _asked_ for my consent to pop-up a modal, I had to click on it because it was so cute and respectful. This is great design that I’m sure converts as well without cheapening your brand and ac…
Agreed. On the other hand, it probably could have done without the sound.
Re: Full-Bleed Layout Using CSS Grid
#63Slightly OT, but this page has the BEST alternative for a modal newsletter pop-up I’ve ever seen. I have a personal rule that I close the tab as soon as a modal asking for my email pops up. When the cute little figure on the left _asked_ for my consent to pop-up a modal, I had to click on it because it was so cute and respectful. This is great design that I’m sure converts as well without cheapening your brand and ac…
Agreed. I subscribed to the newsletter too - I would normally never do that.
Re: Full-Bleed Layout Using CSS Grid
#64Why even use grid when you can solve this much easier without it?
How would you do this otherwise?
A simple implementation that works on IE8 https://twitter.com/e1g/status/1313178559234609153
Re: Full-Bleed Layout Using CSS Grid
#65Slightly OT, but this page has the BEST alternative for a modal newsletter pop-up I’ve ever seen. I have a personal rule that I close the tab as soon as a modal asking for my email pops up. When the cute little figure on the left _asked_ for my consent to pop-up a modal, I had to click on it because it was so cute and respectful. This is great design that I’m sure converts as well without cheapening your brand and ac…
Agreed. On the other hand, it probably could have done without the sound.
ah, my sound was off. That is unnecessarily intrusive.
Re: Full-Bleed Layout Using CSS Grid
#66It’s beyond me why CSS has to be so hard to understand. I have made several attempts and got it right, but it feels like I have to start at zero every time. I believe, it’s because CSS is not a programming language, but we are trying to do programming with it. Like: if screen is mobile then render divs stacked. I don’t know
I think CSS is "difficult to understand" because most people who do front-end don't want to spend a day learning it. Ask some people who make the claim it's difficult: what is the box model, and what is selector specificity. I can almost guarantee they won't be able to answer those questions, because they haven't bothered to actually try to learn CSS. Their knowledge of CSS is built from a set of "how do I do X in CS…
I've been writing CSS for about 10 years at nearly every professional job I've had. I don't get 'stuck' often and generally feel competent, but I am far from an expert or a master. I think CSS is difficult to understand because there are so many ways to accomplish a task, and so many of those ways lead to (sometimes) unforeseeable consequences, and nearly all of the APIs (possibly with the exception of css grid) don't feel very coherent... in my experience. I think it is difficult to learn because there's no real apparent holistic design to really grok.
I tried mdgriffith's elm-ui on a personal project and it was a breath of fresh air. It felt like an utterly excellent abstraction and I hope someone ports it to Typescript/React/JSX some day.
Re: Full-Bleed Layout Using CSS Grid
#67Re: Full-Bleed Layout Using CSS Grid
#68I really hated this era before flexbox and co. CSS used to be the least intuitive thing on the planet yet a lot of people claimed otherwise. We had to resort to silly tricks (remember overflow hidden?) in order to make up for the mess that CSS used to be. Again what really pissed me off isn't CSS inherent issues but the fact that many people claimed there was absolutely nothing wrong with it, a pattern I often see wi…
I find it really frustrating when project runners refuse to acknowledge shortcomings. I'm not always expecting them to solve it, but I'd at least like an acknowledgement that the issue I'm facing is valid. Pretending it's just me or that the obviously worse alternative is okay gets annoying. One example is ReasonML's async story: Q: What's BuckleScript's async story? A: If you're not interfacing with any library that…
This is my biggest bugbear (the general behaviour, not the specific example). I want to make good technical decisions, your library has made choices based on its principles and design goals, don't obscure the trade-offs you've been made -- this is just a (poor) growth hack in disguise.
I've seen so many people use technologies then regret it a year later because they realised what they actually wanted to achieve was at odds with the design goals of the technology.
Re: Full-Bleed Layout Using CSS Grid
#69Earlier quoted context omitted.
How would you do this otherwise?
A simple implementation that works on IE8 https://twitter.com/e1g/status/1313178559234609153
What about inline or inline-block children, such as an aside, a TOC. You are assuming every children is a block. That is not always the case.
Re: Full-Bleed Layout Using CSS Grid
#70Earlier quoted context omitted.
A simple implementation that works on IE8 https://twitter.com/e1g/status/1313178559234609153
What about inline or inline-block children, such as an aside, a TOC. You are assuming every children is a block. That is not always the case.
Nevermind, it's the same with Grid.