v150 · CSS · Typography

Prose Links

Inline links inside article body text — the canonical use case for text-decoration-skip-spaces. With all, the underline hops over every space between words in a multi-word link, keeping the visual grouping tight. With none, underlines run continuously under spaces, merging adjacent links and making long phrases look underlined as a block.

text-decoration-skip-spaces:
all — underline skips all spaces within a link's text, including leading and trailing

The History of the World Wide Web

Tim Berners-Lee invented the World Wide Web while working at CERN in 1989. His original proposal combined hypertext markup language with uniform resource locators and the hypertext transfer protocol into a coherent system for sharing documents over the internet.

The first browser, Mosaic, shipped in 1993 and popularised the graphical user interface for navigating the web. Within two years, Netscape Navigator and Microsoft Internet Explorer were competing for market dominance in what became known as the first browser war.

Modern browsers implement the HTML Living Standard, the CSS specification, and hundreds of web platform APIs across a shared baseline defined by Interop 2025. The open web platform continues to be the world's largest application deployment target, with over five billion active users accessing it via mobile devices, desktop computers, and embedded web views.

skip-spaces: none — spaces underlined
skip-spaces: all — spaces clean

code

/* Article body: skip spaces under all inline links */
.article a {
  text-decoration: underline;
  text-underline-offset: 3px;
  text-decoration-skip-spaces: all; /* Chrome 150 */
}

/* Values:
   none       — underline runs under every character including spaces
   all        — skip spaces at start, end, and within the link
   start      — only skip leading space
   end        — only skip trailing space
   start end  — skip both leading and trailing, not interior (same as all for single words)
*/

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗