Why we should avoid it? Because it can go wrong in so many way. The post describes different cases.

Country flag code to unicode emoji flag

function getFlagEmoji(countryCode) {
  const codePoints = countryCode
    .toUpperCase()
    .split('')
    .map(char =>  127397 + char.charCodeAt());
  return String.fromCodePoint(...codePoints);
}

A HTML validator aiming to be better than the current W3C HTML validator.

There is a descriptive page: https://validator.w3.org/nu/about.html

A great serie of post! Short, simple and clear.

Key takeaways:

• if someone wants high-contrast on some websites, does it mean for every websites?
• go for the accessible version first: high-contrast except for @media (prefers-contrast: less)
• why not fixing color contrast by default?

Some browsers implements customization such as Arc https://resources.arc.net/hc/en-us/articles/19212718608151-Boosts-Customize-Any-Website

It opens new ways to build one-page website too.

I way to style external links in comparison to internal ones.

I would go for the simple css selector a[href^=<domain>]

The mansory layouts is broken for tabbing and keyboard accessibility

Nice example

Simple projects that are handy to learn HTML, CSS and Javascript

Simple explanations of this data structure

but it is still relevant

Insert a code snippet in one line as a bookmark:

javascript: (() => {
// Code here
})();

For example:

• Find a "Jobs", "Careers" or "Hiring" link in the page, and click it.
• Find all email addresses on the current page, and display them in an alert.

These are not limited with permissions, so we should only execute code we checked.

#idea #project a collection of bookmarklet

• IdType trait: a trait that marks a type used for database identifiers
• the read-only/read-write transaction pattern (and create two SQLite connections: a read-only and a write-only)

A way to work with indexedDB in the browser.