Looks like from the source that this would cut the size by 75%.
Show HN: Pattern.css – CSS-only library to fill empty background with patterns
41–50 of 50 posts
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#42Example 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…
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#43Earlier quoted context omitted.
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…
Mono culture provides an average or worse UX experience but the sameness element hits many humans subconsciously. The JS problem was solved with jQuery.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#44Earlier quoted context omitted.
It's not that bad... it's just scrollbars and mobile where things get messy.
Worse than that. Different browsers and different platforms handle scroll bars differently. Some are hidden until hovered and some have width and some don't some only have width when hovered. It's really awful if you're trying to do something with several scrolling columns
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#45I'm guessing it's a bug in Firefox with sub-pixel rounding.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#46Earlier quoted context omitted.
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.
What was Firefox's former behavior for viewport unit handling that other browsers didn't want to go with?
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#47Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#48Earlier quoted context omitted.
Subtle Patterns [1] has been fairly popular throughout the years as well. [1] https://www.toptal.com/designers/subtlepatterns/
Also Transparent Textures ( https://www.transparenttextures.com/ ) – disclaimer, I made it — which is basically Subtle Patterns with a colorwheel that allows the backgrounds to be any color.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#49Earlier quoted context omitted.
Subtle Patterns [1] has been fairly popular throughout the years as well. [1] https://www.toptal.com/designers/subtlepatterns/
Also Transparent Textures ( https://www.transparenttextures.com/ ) – disclaimer, I made it — which is basically Subtle Patterns with a colorwheel that allows the backgrounds to be any color.
Re: Show HN: Pattern.css – CSS-only library to fill empty background with patterns
#50Earlier quoted context omitted.
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…
Mono culture provides an average or worse UX experience but the sameness element hits many humans subconsciously. The JS problem was solved with jQuery.
(That said, the question of when to lean on existing convention vs. establish a new one is a difficult one.)
[1] https://www.nngroup.com/articles/ten-usability-heuristics/ [2] https://www.interaction-design.org/literature/article/princi...