Changelog

• Fix
  Fixed the badge and popup tab counts not going down when notifications were removed or notes marked read in the popup, until the next check or reopening the popup. Removed and read items now come off FurAffinity's totals straight away.
• Fix Firefox only
  Fixed FABUI's features on FurAffinity pages failing behind Cloudflare, including the gallery favorite button (turned orange but didn't favorite) and the uploader ("An error has occurred while loading the FABUI uploader!"). Firefox doesn't send FA's partitioned cf_clearance cookie with requests from content scripts either, so they got Cloudflare's challenge. The clearance listener now adds it to those requests as well.
• Fix Chrome only
  Fixed the upload page closing itself straight away, and continuing to until the extension was disabled and re-enabled (Chrome). Chrome stops FABUI's service worker when idle, which silently dropped the upload page's connection. FABUI kept treating the dead page as an open upload page and closed every new one to avoid duplicates. The service worker now clears connections from its earlier runs on startup, FA pages reconnect when their connection drops (so the upload page can still send uploads after being left idle), and reopening the upload page in the same tab never closes it.
• Contact Developer notes now name the browser (for example "Brave (Chromium 155) on Windows" or "Firefox 158.0 on Windows") and which FABUI build is installed, instead of only the user agent, which reads as "Chrome" for every Chromium-based browser.
• The "View more submissions on FurAffinity" button under the submissions list is now a small text link, so it takes up less space.
• Switching Submissions or Journals off now turns them off for every artist. Per-artist settings can only switch them off further. Previously an artist with their own settings (Journals on by default) kept their journals or submissions coming in and counted in the badge, for example as a green journal count with Journals switched off.
• Fix
  Fixed the "Follows you" check on profiles spinning forever when FurAffinity's watcher list fails to load, for example behind a VPN that Cloudflare challenges. The spinner is now removed.
• Fix
  Fixed the "Follows you" check for usernames containing digits, which were cut short and could match a different watcher whose name started the same way, and for profile URLs with capital letters, which never matched.

• Fix
  Fixed the toolbar badge and popup tab counts including notifications FABUI hides (for example Submissions showing as a blue count with only Notes and Comments enabled). Since 5.16.2 on Chrome, and 5.16.5 on Firefox, counts came from FurAffinity's header totals, which ignore FABUI's settings. FA's totals are now only used for categories that are switched on and not filtered. Switched-off categories, and submissions or journals filtered by a muted artist, an artist's own settings, or blacklist words, are counted from FABUI's own list instead. Settings changes apply to the badge straight away.
• Fix
  Fixed FurAffinity's tag blocklist being ignored, so submissions with blocked tags showed their real thumbnail in the popup and pop-up notifications instead of the FABUI icon. FA's <body> tag spans several lines and the page parser's pattern couldn't match across them. Broken on Chrome since at least 5.16.2, and on Firefox since 5.16.5.
• Fix
  Fixed shout notifications showing no message. FurAffinity moved shouts to its newer comment markup (comment-user-text), which the shout parser didn't look for. Regular comments already handled it.
• Switching off Submissions, Journals or Favorites now clears what was already collected for them straight away, instead of keeping those items until they left FurAffinity's inbox. Submissions and journals from artists whose own settings keep that category on are kept.

First release maintained by Tewulf, taking over from KenjiKuroneki. Chrome and Firefox are now both at 5.16.5 and build from one shared source (src/, platform/, build.py).

• New welcome note introducing Tewulf as maintainer, thanking KenjiKuroneki, and summarising the Cloudflare fixes. It links to Kenji's Ko-Fi (https://ko-fi.com/kenjikuroneki).
• Contact Developer now opens an FA note to tewulf. The Donations option now links to Kenji's Ko-Fi with wording that credits him as FABUI's creator.
• Fix
  Fixed the Contact Developer note template not filling in for versions containing a 0 (the version pattern only allowed digits 1 to 9).
• A new welcome note now replaces any earlier one instead of stacking a new copy on every update.
• Firefox only
  Picks up the shared fixes from 5.16.1 to 5.16.4_1 (FA summary badge counts, "view more submissions" link, dark text on yellow badges, display-name comment usernames).
• Firefox only
  Adds FurAffinity's cf_clearance cookie to the extension's own FA requests (XHR and images) when the browser didn't send it, looked up per request in the existing webRequest listener in js/cookie_fix.js, and rescans as soon as Cloudflare issues a new one.
• Firefox only
  Multi-Account Containers requests now only carry the container's cookies for the request URL, the same set Firefox itself would send. Previously every cookie in the container, for every site, was sent to FA, along with every path's copy of FA's path-scoped cookies. The container's own cf_clearance is included so container uploads aren't challenged.
• Chrome only
  No longer ships js/cookie_fix.js, which was never loaded there.

Follow-up fixes by Tewulf to the Cloudflare clearance handling in 5.16.4. The manifest version is 5.16.4.1 (Chrome only allows digits and dots there) with version_name 5.16.4_1.

• The offscreen document is now created only after the clearance rule is in place, so the first scan after startup is no longer challenged.
• When Cloudflare issues a new cf_clearance cookie, the service worker asks the offscreen document to rescan right away (clearanceUpdated message), so the red "X" clears within a second of opening FurAffinity instead of waiting up to a minute for the next interval.
• Clearance syncs are queued and compared against the value already in the session rule, so overlapping cookie events can't leave the rule empty and service worker restarts don't trigger extra scans.

Fixes by Tewulf for FurAffinity's Cloudflare challenge and 2026 comment layout, based on 5.16.3.

• Fix
  Fixed the red "X" badge caused by FurAffinity's Cloudflare challenge: the partitioned cf_clearance cookie is now appended to the extension's own FA requests (XHR and images) through a declarativeNetRequest session rule in js/service_worker.js. Adds the cookies and declarativeNetRequestWithHostAccess permissions.
• Fix
  Fixed blank comment and shout usernames by reading FA's new .c-usernameBlock .js-displayName markup, and trimmed the custom title shown next to commenters.

Upstream release from the original developer, applied over 5.16.2.

• New
  Added a "Follows you" indicator on user profiles (js/fabu.js checkFollow), paging through the watchlist with the new "Next" form buttons.
• Scoped watchlist parsing in js/background.js to .section-body.watch-list, #userpage-budlist and switched pagination to the "Next" form button.
• New
  Added create: "v2" commission lists (Edit button on existing h1.bbcode_h1 lists) and widened the BBCode marker match from #fabui to #fab.
• Replaced the in-extension announcement with a "FABUI is back on Chrome" notice.
• Updated icons, author (KenjiKuroneki/Tewulf) and the manifest key (this changes the unpacked extension ID).

• Fix
  Fixed notification tab counts by using FurAffinity's summary counts while keeping detail loading to the first message page.
• Kept popup tab badges based on raw notification counts before favorites are grouped or list displays are capped.
• New
  Added a submissions handoff link to FurAffinity when more submissions exist than FABUI loads into the popup.
• Improved yellow toolbar badge contrast by using dark text.

• Fix
  Fixed Brave offscreen contexts where chrome.runtime.getManifest() is unavailable by falling back to the local manifest.json.
• Read transient runtime message errors in the MV3 bridge so closed one-way message ports do not produce unchecked lastError noise.

Manifest V3 port by Tewulf based on the original 5.15.9_0 release.

• Changed manifest.json from Manifest V2 to Manifest V3.
• Replaced the persistent background script declaration with js/service_worker.js.
• New
  Added html/offscreen.html and js/offscreen_bridge.js so the existing background code can keep using DOM parsing, jQuery, audio, blobs, storage, notifications, tabs, windows, runtime messages, and ports from an offscreen document.
• Updated browser_action to action and bridged badge updates through chrome.action.
• Moved FurAffinity and FACDN match patterns into host_permissions.
• New
  Added the offscreen permission and minimum_chrome_version of Chrome 109.
• Converted web_accessible_resources to the Manifest V3 object format with FurAffinity matches.
• Updated js/functions.js to use the MV3 offscreen bridge when it is available.
• Kept js/background.js, uploader, popup, commissions, styles, resources, and audio assets functionally unchanged from 5.15.9_0.