diff --git a/docs/MARKETPLACE-0781-PORT.md b/docs/MARKETPLACE-0781-PORT.md index b037eeef..45fc61f4 100644 --- a/docs/MARKETPLACE-0781-PORT.md +++ b/docs/MARKETPLACE-0781-PORT.md @@ -693,6 +693,35 @@ that fall out of every chip bucket, plus official's two built-in cursor plugins) of "eleven sections here" was a measurement artifact: the catalogue loads asynchronously, and the reading was taken before it had arrived. +**The keyboard focus ring is not official's.** Official 0.78.1's +`.sand-1wpm9rq:focus-visible{outline-color:var(--sand-border-focus-primary)}` resolves to +`#1884fc` on the second-level page's back button, and the rendered outline is a 2 px solid blue +ring. This build renders the same button's ring in the inherited text colour, +`rgba(245, 245, 245, 0.66)`, because two earlier waves left a different rule in front of +official's. The repository's app-link-card port writes an unscoped +`.sand-1wpm9rq:focus-visible{outline-color:var(--sand-border-focus)}`, and the dialog resets +`--sand-border-focus` to `initial` because official does not define it, so that rule falls back to +`currentcolor`. Official's own rule is never reached, because the marketplace companions skip a +rule whose class "already resolves in the dialog" — and the app-link rule makes it look resolved. + +Official's rule is in the companion here, and it is skipped for the same reason. Fixing it is not a +one-line change to the companion: official's blue comes from its runtime theme stylesheet +(`