Collective #587
6.2.2020
Accessible autocomplete control * Octomments * Flow Fields * Binary Search
Collective #587 was written by Pedro Botelho and published on Codrops
Awesome Forward & Reverse Geocoding API: positionstack (Sponsored)
6.2.2020
One awesome web functionality we take for granted is geolocation. Based on geolocation data, we can get someone to their destination, provide them suggestions based on their location, and so on. One downside of native geolocation, especially in the browser, is that it’s limited in both input...
Browser Version Release Spectrum
6.2.2020
Whenever a browser upgrades versions, it's a little marketing event, and rightly so. Looks like for Firefox it's about once a month, Chrome is ~6 weeks, and Safari is once a year.
Chrome 80 just dropped, as they say, and we get a video and blog post. What strikes me about releases like this these...
HTTPS is Easy!
5.2.2020
I've been guilty of publicly bemoaning the complexity of HTTPS. In the past, I've purchased SSL certificates from third-party vendors and had trouble installing them. I've had certificates expire and had to scramble to fix them. I've had to poke and prod hosting companies to help me ensure things...
Native Image Lazy Loading in Chrome Is Way Too Eager
5.2.2020
Interesting research from Aaron Peters on <img loading="lazy" ... >:
On my 13 inch macbook, with Dock positioned on the left, the viewport height in Chrome is 786 pixels so images with loading="lazy" that are more than 4x the viewport down the page are eagerly fetched by Chrome...
WDRL — Edition 281: Progressive Image element, striving for enough, SpiderFoot and the architecture of a web search engine today
5.2.2020
Hey,
There’s so much potential in all of us. There’s so much distraction in our lives today. We tend to continue doing not something different because we have too much on our plates, we are too distracted. We don’t have time to focus on what we really want to do, focus on what we want to change...
CSS4 is a Bad Idea
5.2.2020
Louis Lazaris, reacting to the idea of CSS4:
The reason “CSS3” worked is because it was real. It was the successor to “CSS2.1”. Everything after CSS2.1 was considered to be under the umbrella of “CSS3”.
The gist is that CSS4 isn't real, so won't work, and we don't need it anyway. Perhaps...
Creating an Editable Webpage With Google Spreadsheets and Tabletop.js
5.2.2020
Please raise your hand if you’ve ever faced never-ending content revision requests from your clients. It’s not that the changes themselves are difficult, but wouldn't it be less complicated if clients could just make the revisions themselves? That would save everyone valuable time, and  allow...
Select an Element with a Non-Empty Attribute
5.2.2020
Short answer:
[data-foo]:not([data-foo=""] {
Longer answer (same conclusion, just an explanation on why we might need this):
Say you have an element that you style with a special data-attribute:
<div data-highlight="product"</div
You want to target that element and do special things when...
Crafting a Cutout Collage Layout with CSS Grid and Clip-path
5.2.2020
Learn how to code up an interesting design with a cutout image look using CSS Grid and clip-path.
Crafting a Cutout Collage Layout with CSS Grid and Clip-path was written by Briana Camp and published on Codrops
CSS4
4.2.2020
Tab Atkins in 2012:
There has never been a CSS4. There will never be a CSS4. CSS4 is not a thing that exists.
Rachel Andrew in 2016:
While referring to all new CSS as CSS3 worked for a short time, it doesn’t reflect the reality of where CSS is today. If you read something...
How To Create A Headless WordPress Site On The JAMstack
4.2.2020
Just this morning, Chris shared a streamlined way to get a static site up and running with Netlify. As it happens, Sarah and I also wrote up a little something that expands that idea where a static site can pull content from WordPress using the REST API.
Using Vue, Nuxt, axios and Netlify, it's...