/* ====================================================================
motion.css — the motion and finish layer, shared by both trees.
Load order. This file is LAST in both s: after style.css on the
English tree, after style.rtl.css + fa.css on the Persian one. Being
last is what lets a plain, low-specificity selector here beat a theme
rule of equal weight, which two sections below rely on.
ONE FILE, BOTH DIRECTIONS. Every rule here is either direction-neutral
or carries an explicit [dir="rtl"] companion. So:
DO NOT run this file through rtlcss.
style.rtl.css is a generated artifact; this one is hand-written, and
flipping it would double-flip the two rules that are already handled.
Three rules the file keeps, and that anything added to it must keep:
1. No CDN, no @import, no external host of any kind. The Persian
tree serves visitors inside Iran, where Google Fonts, jsDelivr,
unpkg and cdnjs are all unreachable. The only URL below is an
inline data: URI.
2. Nothing hides content unless the thing that would reveal it is
known to work. Every rule that starts an element at opacity 0
sits inside an @supports block for the feature that animates it
back. A browser without the feature never runs the rule, so it
never has content stuck invisible — the failure mode of every
scroll-animation library that ships without this guard.
3. prefers-reduced-motion: reduce turns off everything that moves
by itself. style.css honours that preference in 44 places and
this file is not going to be the exception.
One deliberate exception, section 1: the reading-progress bar
moves only in direct response to the user's own scrolling, in
lockstep with it, like a scrollbar. It starts nothing, it
cannot surprise anyone, and removing the only affordance that
says "how far down am I" is not an accessibility win.
Nothing in this file is required for the page to be usable. It is all
finish. If any of it misbehaves, deleting the two /