Love it!
Site could use some help though. Consider making a repo for the actual website please! Would love to help clean it up a bit.
Show HN: Pattern.css – CSS-only library to fill empty background with patterns
21–30 of 50 posts
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#22I bet this will the hottest web-design trend for next two years.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#23Earlier quoted context omitted.
Can you provide a screenshot?
https://imgur.com/ts3ashk Some of your background boxes overlap with the sidebar.
Same in Chrome: https://i.imgur.com/0zcCqD6.png
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#24If you don't need to install stuff from npm and prefer to hack your own, here's a nice list of CSS patterns to get you started: https://leaverou.github.io/css3patterns/
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#25Example site ( https://bansal.io/pattern-css ) misrendered in Vivaldi, which brings me back PTSD grade memories about the browser war and css bugs, implementation-diferences, etc. So let me ask, how is it possible on the almost completely monoculturized web, where is no Presto and almost no Trident anymore, where almost every browser is kind of chrome-isotope. So let me ask, maybe a web developer cn answer me: what i…
As a user, I'm all for browser choice in the abstract: it sounds like a good thing, but it doesn't often deliver me tangible benefits in usability, performance, etc. (And, to wit, the only real exceptions are when large organizations bankroll extensive browser development teams.) As a developer: even with several browsers converging on the same renderer and JS runtime, it is _still untrue_ that all things work in all…
I wish browsers were more modular so you could switch the underlying engines, sandboxes, and stuff. Don't want js? Remove the js engine. Don't want css? Remove that part. Don't want webrtc? Remove that. Compile your own flavor bloat free.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#26Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#27Also see Hero Patterns: http://www.heropatterns.com by Steve Schoger.
i have more here, and just added some by you https://github.com/sw-yx/spark-joy/blob/master/README.md#use...
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#28The website https://bansal.io/pattern-css was clearly produced on a platform with overlay scrollbars. There are a number of horizontal scrollbars that shouldn’t be there.
.overflow-scroll {
overflow: scroll !important;
}
.w-100vw {
width: 100vw !important;
}
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#29The website https://bansal.io/pattern-css was clearly produced on a platform with overlay scrollbars. There are a number of horizontal scrollbars that shouldn’t be there. .overflow-scroll { overflow: scroll !important; } `overflow: scroll` is pretty much never what you want: it draws scrollbars whether needed or not. You want `overflow: auto` instead, which doesn’t draw scrollbars unless necessary. .w-100vw { width:…
> Viewport units are fundamentally broken by design. Don’t ever use them for layout. In fact I recommend against using them in any situation at all.
That's a pretty bold claim. Can you elaborate on that?
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#30The website https://bansal.io/pattern-css was clearly produced on a platform with overlay scrollbars. There are a number of horizontal scrollbars that shouldn’t be there. .overflow-scroll { overflow: scroll !important; } `overflow: scroll` is pretty much never what you want: it draws scrollbars whether needed or not. You want `overflow: auto` instead, which doesn’t draw scrollbars unless necessary. .w-100vw { width:…
> Viewport units are fundamentally broken by design. Don’t ever use them for layout. In fact I recommend against using them in any situation at all. That's a pretty bold claim. Can you elaborate on that?
Some comments I’ve made here on the topic:
https://news.ycombinator.com/item?id=21244656
https://news.ycombinator.com/item?id=20956850
The currently-implemented viewport units are just fundamentally bad. And I’ve only been talking about the badness of vw; vh has further troubles of its own on mobile.