Based on the findings here it would make a lot of sense to be able to disable the behaviour of having localisation on the focal point fields.
Especially with project we’re working on (20+ locales) where the website is setup with a site builder (Multiple modular blocks) it is a lot of work for our users to modify the focal point.
Focal point is localised?! I’m not surre it makes sense at all to be localised. I’d advocate to disable this entirely, it’s almost a bug!
I’ve let our UX designer know about this situation as well. No work is currently planned on it, but I agree that this is less than ideal!
In the meantime, I just wanted to share a workaround…
Normally, if you make a GraphQL query in a specific locale, you get all the metadata in that locale (alt text and focal point):
But you can override this by specifying a hardcoded locale just for the focalPoint, like this:
query MyQuery {
english: upload(locale: en) {
...UploadFragment
}
italian: upload(locale: it) {
...UploadFragment
}
}
fragment UploadFragment on FileField {
alt
focalPoint(locale: en) { # Hardcode your primary locale as an override
x
y
}
}
That way, your different locales can still get localized captions, but all of them can use the same focal point.
That doesn’t altogether solve this feature request, but hopefully it’s a better-than-nothing workaround for now.
@here This has been launched! Please give it a try and let us know if you have any feedback.
What changes for everyone today
Every asset now has a single focal point: one value, shared across all locales. This isn’t an opt-in. It applies to every project right away.
Cropping is now consistent across languages. Set the focal point once, and it applies in every locale. If you were only setting it in your primary locale (as most people were), your crops everywhere else just improved on their own, with nothing for you to do.
Optionally, you can also opt-in your projects to a simpler CMA shape for focal points: A tidier CMA format for focal points — DatoCMS Product Updates