CSS Layout and Font Integration Trip Up Developers
Developers of varying skill levels are facing challenges with CSS, ranging from teaching it to beginners, managing layout shifts, achieving modern aesthetics, and integrating custom fonts. The core pain revolves around the complexity and nuances of CSS, hindering efficient workflow and project completion. Many seek simpler solutions or better learning resources.
SOURCES (60)
“One useful sanity check: `parseFloat(getComputedStyle(document.documentElement).fontSize)` gives the current root size in CSS px. If you compare it with `getBoundingClientRect()`, both values are also in CSS px; `devicePixelRatio` only comes in when converting to device pixels. Mixing those units is an easy way to make a…”
“Repost of https://www.reddit.com/r/webdev/comments/1wv6zx0/the_dropdown_behind_the_curtain_a_wizard_of_oz/”
“I’ve been burned by this exact headache so many times. The Teleport fix is the only thing that finally makes sense to me”
“Thanks for building OGraf Studio. Would support for author chosen element keys be something you’d consider? It would be useful to assign a stable key (for example, scoreline ) to any element in Studio and make the corresponding element discoverable by JavaScript alongside the exported graphic. This would let external tools identify elements without relying on generated IDs. Is this on your roadmap, or does it fit the direction you have in mind? We’re open to your preferred approach. Thanks for c”
“Oh okay I actually first discovered this font on a screenshot from the developer of the GitFourchette app , specifically the Inter Display variant, and am using it as a system-wide font, which I like a lot, especially on KDE Plasma. For content though, my favourite font is Helvetica.”
“Yep, we're calling out when fonts have been substituted, but if the user opens it on the same machine they created it on, it should have the fonts and look the same.”
“the font swap is what will make a church bulletin look wrong even if the boxes land in the right place. if the computer doesn't have the old Publisher font, the line breaks change and the page-for-page claim falls apart. embedding those fonts, or at least flagging the missing ones before they print, matters more than the ribbon looking familiar.”
“Unfortunately, for me, any plugin which still requires the user write ugly code blocks to do the most basic document layout stuff is a no from me.”
“I enjoy trying out new themes and just installed it. I like the color pallet, but there are not many customizations in style settings. I like to customize typography in a theme, including the font size. Also some themes let you dim images. Since you find screen comfort important it's worth adding.”
“the term you want to search for is "news ticker" or "scrolling ticker" tutorial. that'll get you way better results than "scrolling text" which mostly returns star wars intro stuff. once you know the right keyword it gets a lot easier to find what you need”
“This is a good question and something I want to experiment with and something I should definitely document, I just haven’t had the chance. Atm overriding via Class is done by appending to the order using ClassBuilder there’s no conflict or merge resolution, so the same property utility clashes are exposed to Tailwinds CSS output order rather than a pre-determined override. The typed variant props e.g Enums like (Color, Variant, Rounded, Shadow) are the reliable override path; raw utility overrid”
“I've been using Blazor professionally for a couple years and the styling problem you describe is painfully real. MudBlazor and Fluent UI are fine for internal dashboards, but any client-facing project turns into an override-CSS war the moment designs don't match their default look. Going typed Tailwind classes at the component level is the right escape. Starred.”
“现状 CLI 与 VSCode 插件都很好用，但插件 UI 目前是英文硬编码： 插件没有 package.nls .json / l10n 目录，webview（resources/webview.html）与 package.json 命令标题均为硬编码英文 而仓库的 templates/prompts、docs、README 已经有完整中文内容——项目本身是中文生态，只是前端 UI 漏了 i18n 涉及的主要界面文案（已梳理） 顶部/发送区：New chat / Send / Stop / Write a prompt... / Search sessions... 技能弹窗：Select Skills / Skill / No skills found 权限弹窗：Permission required / Permission denied / Yes / Yes, and always allow this scope / Interrupt 气泡区：Thinking / Skills / Copy 上下文仪表：Context Window / session.usage /”
“first time checking out CSS snippets - it worked, thanks a bunch in case somebody happens to look for this: body { `--tab-background-active: #073763;` --tab-outline-color: #ffa300; --tab-font-size: 0.85em; } .workspace-tab-header.is-active { `font-weight: 500;` } works great for me with "Typewriter" as my Theme in Dark Base color scheme.”
“Heya! I am here asking if you could add an option to maintain some custom css. I use some css for italics, bold and also a plugin named fast text color to change the aesthetics of some text (color, font size, highlights, etc.) as it helps with a lot of studies and documents. The plugin is very nice, it exports a lot better than native pdf export (even with media print css) and it organizes better, its more elegant, so I think it could be a good addition if it could be done, of course, and let us”
“Re: CSS, it is indeed declarative, that was a bit sloppy of me. My comparison rests on observed difficulties. Valid CSS can contain duplicates, overwrites, or coupled parent-child pairs as in a grid, or mistaken use of properties that have no effect without other properties. CSS allows disciplined decomposition and separation of concerns, but does not enforce it. We all seem to agree this is the RightThing(tm), but it means CSS fails on practical grounds when compared to, for example, SQL DDL”
“Someone shared this plugin to the sub a few days ago. It sounds like it matches your use case.”
“Sure, the thing is that the user could have browser settings or an extension that forces a higher font size for accessibility reasons and so it’s nice to have a solution that can survive all that 😮💨”
“Never seen round() used on a length like that, good to know it holds up. The bit that catches people is that round() with a unit in the second argument is newer than most of the syntax guides show, so it silently fails on older Safari and you're back to the wobble. I usually set the spinner to a fixed px size and scale the wrapper with transform instead, since the rotation stays smooth and you don't depend on font metrics at all. Does it hold when the user has a large minimum font size s”
“I haven't run into this because my 1em values almost always land on an even number (does anybody else use font sizes of 0.875/0.75/0.625rem?), but this is an excellent reminder and use case for round(”
“your template only runs once because of the ids. getElementById on precon can only ever hand back one element, and temptit, tempdesc and tempimg are ids too, so if you have five project blocks reusing those same ids the browser gives you the first and quietly ignores the rest. thats not you being bad at js, thats the html model. turn every one of those into a class, grab the blocks with querySelectorAll, loop, and the code you already wrote starts working. that said id not keep the data in the d”
“Checks [x] This is not a duplicate of an existing issue (please have a look through our open issues list to make sure) [x] I have thoroughly read and understand The Odin Project Contributing Guide [x] Would you like to work on this issue? Describe your suggestion I found this video very helpful in clearing concept, idea, knowledge & real time application of css position. So, I vouch for this to be added. After watching this video, I understood that how position:fixed works with scrolling, differ”
“Amazing But I wasn't able to completely destroy client site for example icons ( font-family: icomoon ) rendered using before and after in the CSS can't be destroyed, right?”
“Reading mode CSS is working fine, but the editor one isn't, maybe it was broken by the new update. Check whether if you have any css or other modification or theme which is creating problems.”
“So you kind of end up back at the same place, where some elements need their own specific values”
“Sure, and I do in many cases. But then you also have to do stuff like having css vars in your inline styles to define the variables...”
“Humans aren't reading the html. And the "bloat" is compressed away. Layout and Style isn't separate concerns. You've literally never made an app that had it's structure not influenced by the styling and styling not influenced by the structure. That's just outright stupid.”
“because that assumes you want the css variables to change universally at a specific breakpoint, while that might not be true...”
“You really think something like a custom BEM system is easier to maintain and more consistent than centralized and professionally documented utility styles? The internet has changed a lot since the 90s, there’s no need to stick to conventions from then”
“Sometimes inline styles can be useful for critical css. It's quicker than loading a stylesheet obvs. Like anything, if used in moderation and with good reason.”
“Example these tables are supposed to line up <img width="1680" height="1379" alt="Image" src="https://github.com/user attachments/assets/e51c1688 e22a 4afe 9c17 026a6a43e07c" /”
“At work, we've have a rule that says we're not allowed to use inline styles. The rule originated a while ago, from people who have long since left the company, and we've been carrying it on. I'm thinking about challenging it, and have been researching into why this seems to be a common "best practice". Most discussions I find on the subject are about a decade old, which is why I thought I'd bring up for discussion on Reddit as well, to see what people now days have”
“When I had to use tailwind, I did it often, because we used the default config, which for whatever reason uses rem units for everything, and there were many times I needed to use px units instead 🤷♂️ I'm sure we could have done something in the config to change this. But also, there's not really much difference between saying "m-16" for "margin: 16px" (assuming we adjusted the config to make this translation), vs just doing [16px] directly.”
“To the uninitiated, it can *appear* that way. But once you’re familiar with the framework, it makes good sense. And it’s better than trying to remember what some custom style may be. With tailwind it’s right there, easy to see. Moreover, tailwind blends well with front end components. Style the component once with tailwind. To later change the style of a component, just edit the component directly. Cascading, yes. Hence, my use of the word. The popularity of any web technology may vary, dependin”
“If you don't care how your site gets styled, only that it does get styled, use tailwind. If you want to maximize performance or simply avoid relearning CSS in a different syntax then use CSS. Ultimately it's not going to make a huge difference. I personally prefer vanilla CSS, particularly when using a component framework that handles scoped styles (as any respectable framework does), but if I'm using something like React then tailwind fits into the "easiest, not best" vibe”
“You’ve got that the wrong way around. Tailwind is probably unnecessary for small projects, but invaluable for medium or large projects, especially with a team.”
“I really love Tailwind for some projects, but saying plain CSS is tedious in 2026 is ridiculous. CSS has evolved so much that it now offers many tools that make plain CSS usage very relevant in a lot of cases. I remember when we had to chose between SCSS or any CSS+ wrapper to compensate some missing features in CSS, this is not the case anymore so if you enjoy CSS, just continue with it. In professional environments, you will often see Tailwind, but, if you master CSS, it’s like an afternoon of”
“You work in a team or on a project that you'll leave to someone else, and you're using a JS framework : Please use tailwind. Regardless how clean your css is, your teammates aren't always as clean as you are, and having multiple classes do the same thing slightly differently is a chore to maintain. And more often than not it ends in cascade hell. If you work alone on a project that won't be maintained by anyone else, do write css.”
“Indeed, the reason this was a problem, imho, was because it’s hard to manage everyone’s specific opinions on how styles should be managed. So by standardising this you get maintainable code everyone can work on aka collaboration. But maybe I missed something, it has been a while since I actively did webdevelopment”
“Tailwind saves you from inventing class names and jumping between HTML and separate stylesheets. It also enforces consistent design tokens and outputs tiny production‑ready CSS. advice: test it on some small side‑project. If it clicks for you, adopt it. If not, stick with plain CSS ：）”
“I hate all the classes it adds to html. For me that alone is the major thing holding me back from using it.”
“Index + offset as the canonical position is the right call, and the underrated consequence is that the scrollbar becomes a derived, lossy thing instead of the source of truth. Two questions from someone who has shipped a jittery feed: what happens on scroll restoration after a refresh when row 8000 now measures differently, and how do you serve a find-in-page or anchor jump that wants a pixel target you don't have? A global pixel map buys you exactly one thing, random access, and most feeds”
“I would say the only reason we use frameworks is for collaboration and standardisation. I am sure this was not the sauce under which tailwind was initially sold. It was supposed to address the problem of organising the styles: their co-location with markup, and their reuse.”
“I don’t like Tailwind CSS. Mixing HTML and CSS classes in the same file makes components messy. Tailwind CSS may be good for small projects, but for medium-sized or large projects, I think it’s a bad solution.”
“I think that's an original issue though.Accessibility certainly requires a content-first approach, I agree with you there. If you view each part of an application solely in terms of what it looks like to a sighted user, it's easy to miss the subtleties of what the underlying structure ought to be.But when you start layering on the presentation, you're still generally binding that presentation layer tightly to the current content. If you, for example, were to restructure the links in the Zen Gard”
“I still have their flexbox and grid cheatsheet as bookmarks and still use them as I don't often do frontend work”
“I’m working on a VS Code extension that uses before / after decoration attachments to show small inline indicators next to CSS declarations. I ran into a limitation with the current API: there doesn’t seem to be a way to set the cursor for an attachment itself. For example, I’d like to be able to do something like: This would be useful for extensions that render inline icons or indicators that are interactive, where changing the cursor only when it is over the attachment would make it clear that”