The Entity translation patch wrongly used a variable in the JS. It's not selecting the right element.

This shouldn't be an issue in real life since FAPI gives unique enough class names, but it's inconsistent and might be an issue at some point.

CommentFileSizeAuthor
core-js-et-sumary.patch465 bytesnod_

Comments

seutje’s picture

seutje commented
Status: Needs review » Reviewed & tested by the community

Makes sense, although I can't think of a use-case where the context passed in would differ from the one in the higher scope, this is how the API is designed to work.

Also, love the French patch name :P

nod_’s picture

nod_
Primary language French
Location Lille
commented

et = entity translation, sorry to disappoint :p

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Reviewed & tested by the community » Fixed

Committed and pushed to 8.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.