Not calling it a bug yet.

Prerequisite to #2451657: Views should not condition joins on the langcode of fields that are not translatable

1. Create a new integer field on the first one,
2. Reuse the field on the second content type.
3. Export the configuration of both fields

The first has:
translatable: true

The second has:
translatable: false

Comments

lokapujya created an issue. See original summary.

lokapujya’s picture

lokapujya
Primary language English
Location Boston
CreditAttribution: lokapujya at Babson College commented
Issue summary: View changes
Issue tags: -VDC, -D8MI, -language-content, -Barcelona2015, -rc target, -Needs tests, -Triaged core major
dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented

This seems to be a valid behaviour, don't you think so?

lokapujya’s picture

lokapujya
Primary language English
Location Boston
CreditAttribution: lokapujya at Babson College commented
Status: Active » Closed (works as designed)

Yeah, it's actually a misconfiguration problem.