## **Problem** A code component's **content-entity-reference** prop exposes fields of a referenced content entity to the component (via `dataDependencies.entityFields`). On a multilingual site those field values were read in the **referenced entity's own default language**, ignoring the language the host page is rendered in. Repro: a page translated to Spanish, a code component referencing a node that has a Spanish translation. Translating both the host and the referenced entity (e.g. via TMGMT) does not help — the component still receives the referenced node's **English** values. ## **Root cause** Every other prop-source path already resolves referenced entities in the host entity's language: `EntityFieldPropSource` and `StaticPropSource` pass `NegotiatedLanguage::matchEntity($host_entity)` into the evaluator, whose reference branches call `Evaluator::resolveTranslation()`. `JsComponent::buildReferencePayload()` was the sole exception: it read the referenced entity's fields with `NegotiatedLanguage::matchEntity($referenced_entity)` — the referenced entity's _own_ language — and the expression that produced that entity (a `FieldPropExpression` ending in `entity`) never ran it through `resolveTranslation()`, so it arrived in its default language.