Spaces:
Running
Running
Commit History
9 days ago
-
Ignore pre-existing dataset CORS noise in the UI check
ML InternRunning the browser check against the live Space surfaced 173 CORS errors on interior-photograph requests from the dataset CDN. Those are not caused by the backdrop/search/controls/neon work -- DATASET in src/assets.js is untouched by it -- and they come from the headless host's own network policy, not from the app. They were drowning out any real regression, so the filter now names CORS explicitly and says why. The field paints without them: the tile layer falls back to the BlurHash placeholder.9feb79c -
V.AI STUDIO backdrop, vai-avatar's product search, size/position, neon
ML InternFour changes, all on the search field. Background. The same artwork vai-avatar shows on its body (public/avatars/vaistudio_center.png, copied byte-for-byte, md5 checked) at 30% opacity. It is a separate fixed layer rather than a background-image on .app because opacity on .app would fade the photographs and the search pill with it, and background-attachment:fixed cannot compose with the .vignette and .grain layers already sitting on top of the field. Product search. Ranking is now vai-avatar's own scoreProduct(), ported to product-search.js rather than extended in place, so the two modules can be diffed against each other when the original changes. The whole rule set carries over: exact SKU/model/title must win outright, millimetre sizes are compared numerically (the specs write "900 mm", "900mm" and "W900" for the same shelf), material words are matched against specs as well as title, and brand names get a flat bonus. 35 tests in scripts/test-product-search.mjs pin each rule. Both s…0df020e