Our approach
Following the overlooked
We started Curious Button Rang because the best part of a website is often a two-word button nobody mentions. This page explains how we choose what to write about, how we check it, and what we refuse to do.
Method
Documented first, playful second
Every entry separates two things. Documented marks behaviour we have confirmed in official help pages, release notes, standards documents, the creators' own statements or reliable contemporary reporting. Our reading marks interpretation: why we think a design works, what it might say about its makers, and occasionally a joke.
We test browser features in current releases of Chrome, Edge, Firefox and Safari before publishing, and we re-check entries when major versions ship. Where credit for a pattern is disputed, we name who is most widely credited and say that it is shared.
Primary sources
Mozilla and Google support pages, W3C specifications such as WCAG 2.2, and interviews with creators.
Dated checks
Browsers ship updates every few weeks, so each file carries a published date and is reviewed when things change.
Safe by default
We never publish tricks for bypassing logins, paywalls, age checks or security prompts, and we never promise “secret access”.
Independence
No sponsors in the ledger
Curious Button Rang is published by Curious Button Rang Publishing Ltd and is not affiliated with Google, Mozilla, Apple, Microsoft, Reddit, or any studio or creator we feature. We do not accept payment, free products or affiliate commissions for inclusion, and there are no adverts on the site.
If we make an error, email [email protected]. We fix mistakes openly and note significant changes at the end of the entry.
“We explain the design, not the way around it.”— From our editorial guidelines
Contributors
The people keeping the ledger
Imogen Vale
Founding editor
A former usability researcher who has spent too many afternoons timing how long people take to find a cancel button. She writes the Hidden Controls and Clever Interfaces files.
Tobias Okafor
Browser features researcher
A front-end developer who reads browser release notes for pleasure. He tests every shortcut and internal page we describe, on four browsers and two operating systems.