AI Trace azray n lqem - 4 ileqman
AI Trace sɣur Trace Foundation
AI Trace azray n lqem - 4 ileqman
Ɣur-k ɣef yileqman yezrin! TTwaseknen-d kan i usekyed akked umuqel.Yessefk yal tikkelt ad tesqedceḍ lqem aneggaru n uzegrir.
Lqem aneggaru
Lqem 1.0.3
Yeffeɣ-d deg 11 apr. 2026 - 32,12 KBIteddu d firefox 121.0 d yileqman imaynutenv1.0.3 - Apex redirect fix + popup render fix- Fixed: Extension still showed "Unable to reach AI Trace"
on every website in Firefox after v1.0.2. The onMessage
Promise rewrite in v1.0.2 was correct but irrelevant; the
real blocker was that host_permissions only covered
https://aitrace.org/, while the server 308-redirects
every apex request to https://www.aitrace.org/. Firefox
MV3 service-worker fetch() will not follow a redirect to
a host outside host_permissions, so every fetch threw a
network error before any response body was read. Added
https://www.aitrace.org/* to host_permissions so Firefox
allows the redirect chain through. - Fixed: After a successful fetch, the popup rendered the
loading spinner stacked on top of the company profile.
Root cause was a CSS specificity bug in popup.css:
#state-loading { display: flex } at specificity (1,0,0)
outranked .state[hidden] { display: none } at (0,2,0), so
setting the hidden attribute on #state-loading had no
effect. Added !important to the .state[hidden] rule so
every state honors the hidden attribute regardless of
any per-state display override. - Added: jsdom-based regression test
(src/tests/v2/extension/popup-css.test.ts) that parses
popup.html + popup.css and asserts every .state element
collapses to display:none when hidden is set. Reproduces
the v1.0.2 bug; guards against recurrence. - No new permissions, no new data collection.
Tangalt taɣbalut teffeɣ-d s turagt Akk izerfan ttwaḥerzen
- Fixed: Extension still showed "Unable to reach AI Trace"
Ileqman iqbuṛen
Lqem 1.0.2
Yeffeɣ-d deg 11 apr. 2026 - 31,99 KBIteddu d firefox 121.0 d yileqman imaynutenv1.0.2 - Firefox compatibility fix- Fixed: API calls failing on all websites in Firefox. Every
page showed "Unable to reach AI Trace". Root cause: the
runtime.onMessage listener used the Chrome-only
sendResponse + return true pattern. Firefox ignores both
and only resolves replies through a Promise returned
directly from the listener. Rewrote the listener to
return the async IIFE directly. Chrome MV3 (99+) supports
this pattern natively, so it is fully cross-browser. - Added data_collection_permissions: { required: ["none"] }
per the new Firefox built-in data consent requirement. The
extension collects no user data: URL is read locally, only
the derived company slug is sent to the public API. - Manifest background declares both service_worker and
scripts for Firefox AMO compatibility. - gecko strict_min_version is 121.0 (required for
service_worker support in MV3 under Firefox). - No new permissions added.
Tangalt taɣbalut teffeɣ-d s turagt Akk izerfan ttwaḥerzen
- Fixed: API calls failing on all websites in Firefox. Every
Lqem 1.0.1
Yeffeɣ-d deg 11 apr. 2026 - 29,65 KBIteddu d firefox 121.0 d yileqman imaynutenv1.0.1 - Firefox compatibility fix- Fixed: API calls failing on all websites in Firefox.
Root cause was the onMessage listener using a Chrome-only
async pattern (bare IIFE with sendResponse). Replaced with
promise.then(sendResponse) which works cross-browser. - Bumped gecko strict_min_version from 109.0 to 121.0
(required for service_worker support in MV3). - Broadened host_permissions pattern.
- No new permissions added.
Tangalt taɣbalut teffeɣ-d s turagt Akk izerfan ttwaḥerzen
- Fixed: API calls failing on all websites in Firefox.
Lqem 1.0.0
Yeffeɣ-d deg 8 apr. 2026 - 25,88 KBIteddu d firefox 109.0 d yileqman imaynutenTangalt taɣbalut teffeɣ-d s turagt Akk izerfan ttwaḥerzen