content/notes/borrowing-from-big-players.md

@@ -5,7 +5,7 @@ replyURI: "https://adrianroselli.com/2020/03/i-dont-care-what-google-or-apple-or
 replyTitle: "I Don’t Care What Google or Apple or Whoever Did"
 replyType: "BlogPosting"
 replyAuthor: "Adrian Roselli"
-replyAuthorURI: "https://adrianroselli.com/"
+replyAuthorURI: "https://adrianroselli.com/posts"
 ---
 Large organizations' choices influence my decisions in only one way: by telling me what users are familiar with. For instance: when building a search-results page, it might make sense to borrow the basic semantics of existing search engines (Google, Bing, etc.) so the interface is familiar.
 

content/notes/firefox-focus-ring-regression.md

@@ -7,11 +7,9 @@ syndicatedCopies:
     - title: 'IndieNews'
       url: 'https://news.indieweb.org/en'
 ---
+
 Firefox 120 appears to have regressed to its older WebKit-like blue focus outlines; it briefly had dual-color white-and-blue outlines.
 
 I'd previously advised certain sites (sites with background colors that have poor contrast against the focus-ring's blue color) to override the default focus indicators. I planned to temper that advice since Chromium and Firefox adopted focus indicators that appeared visible on a variety of background colors; I suppose I should cancel those plans.
 
 As long as people have to use defaults they didn't choose (e.g. Tor Browser users are stuck with default settings), we have to override them when they're inaccessible. We can't count on users to always have the means to do this: fingerprinting concerns and device-borrowing are facts of life.
-
-<ins datetime="2023-12-06T05:53:35+00:00">Update <time datetime="2023-12-06T05:53:35+00:00">2023-12-06</time>: it appears that as of Firefox 121, the issue only appears in forced-colors mode (e.g. when toggling color overrides in the color settings of `about:preferences`). Input elements are unaffected. With forced-colors disabled, Firefox uses the better two-tone indicator.</ins>
-