Bram.us, curated by Bram Van Damme, is a  web development blog offering tutorials, guides, and insights into various aspects of frontend and backend development. With a focus on modern web technologies such as HTML5, CSS3, and JavaScript frameworks like Vue.js and React, Bram.us covers topics ranging from responsive web design to server-side scripting with PHP and Node.js. Developers can learn about  web development techniques, browser APIs, and best practices for building fast, accessible, and user-friendly websites and web applications.

Bram.us

view-transitions-mock is a non-visual polyfill for the Same-Document View Transitions API, created to eliminate the need for defensive browser-support checks in your code. It implements the full JavaScript API surface of the View Transition spec (including ViewTransition promises, transitionRoot, activeViewTransition, and View Transition Types) without polyfilling the visual/animation aspects. Install via npm, call register() before using document.startViewTransition(), and your code runs without errors in all browsers. Registration can be tuned with requireTypes and forced options for fine-grained control.

Introducing view-transitions-mock: A non-visual Polyfill for Same-Document View Transitions

Not sure why this guy wrote this polyfill, if the View Transitions feature supported almost in all browsers now:
<img src="https://media.daily.dev/image/upload/s--pGRyVu1P--/f_auto/v1773218518/ugc/content_e0dc4c0f-9b9f-488c-bfe3-f22037cab42a?_a=BAMAMiiu0" alt="Bildschirmfoto 2026-03-11 um 09.41.48.png">
Another question is “why should I use it?” --&gt; to fill 1% gap like IE, QQ or KaiOS browsers? 🤔