Web Compatibility Support • Re: One Minor and One Major Issue at Intel website ( https://www.intel.com/content/www/us/en/homepage.html )

I worked with AI on this a bit this morning, and found the page uses Coveo Atomic Web Components. On this page, Pale Moon loads Coveo Atomic v3.31.1 and Coveo Headless v3.27.7. The CoveoAtomic global exists, and Intel’s atomicSearch config object exists. The page fetches atomic.esm.js, index.js, index-Ck3d7uJy.js, atomic-search-interface.entry, atomic-search-box.entry, atomic-facet.entry, atomic-category-facet.entry, atomic-folded-result-list.entry, headless.esm.js, and many related Coveo/StenciI helper chunks.

However, the Atomic components do not hydrate. Scratchpad tests show:

CODE:

typeof customElements = objectcustomElements.get("atomic-search-interface") = function / presentcustomElements.get("atomic-search-box") = function / presentcustomElements.get("atomic-facet") = function / presentcustomElements.get("atomic-category-facet") = function / presentatomic-search-interface exists = truehas initialize method = functionhas executeFirstSearch method = functioncomponentOnReady = functionshadowRoot = YESshadow DOM children = 0has hydrated class = falsevisibility = hiddencomponentOnReady() does not resolve after 5 seconds

The CSS includes the typical Stencil pre-hydration rule that hides atomic-* elements until .hydrated appears:

CODE:

atomic-... { visibility: hidden; }.hydrated { visibility: inherit; }

The Error Console then logs repeated errors like:

CODE:

Error: Constructor for "atomic-search-interface#undefined" was not foundSource File: https://static.cloud.coveo.com/atomic/v3.31.1/index-Ck3d7uJy.jsLine: 2096

Similar errors occur for atomic-search-box, atomic-facet, atomic-category-facet, atomic-result-template, atomic-pager, atomic-query-summary, and other Atomic components.

So the page appears to get past basic custom-element registration and script fetching, but fails during Stencil/Coveo component hydration or constructor resolution. The elements are registered and upgraded enough to expose methods, but first render never completes, shadow DOM remains empty, and .hydrated is never applied.

I also tested the page with filters created for the Pale Moon Modify HTTP Response extension by JustOff. Patching atomic.esm.js successfully injected code, so the external module response is definitely executing in Pale Moon. A shim for CSSStyleSheet.prototype.replace, CSSStyleSheet.prototype.replaceSync, and adoptedStyleSheets did run but did not fix hydration, so missing Constructable Stylesheets alone does not appear to be sufficient to explain the failure.