WAIT: Honeypot visible on translated pages on MacOS, with Polylang

Browser: Chrome
OS: macOS
URL: https://gms-cyprus.com
Video: As I’m on Windows I cannot record a video.
Bricks version: 2.1.3

I’m not sure if this is an actual bug, or just some issue specific to the website. I have a contact form built with Bricks, and I’m using Polylang for translation. My client today sent me a screenshot that the contact form on our Russian page Медицинский туризм на Кипре. Хирурги мирового класса из Израиля, стран ЕС и США - GMS | General Medical Services (bottom of the page) is not working. The issue is that the honeypot field is visible on translated pages only (Медицинский туризм на Кипре. Хирурги мирового класса из Израиля, стран ЕС и США - GMS | General Medical Services and GMS Cyprus: Medical Tourism in Cyprus With World-Class Surgeons - العربية - GMS | General Medical Services). On the base language, the honeypot is not visible. This only occurs in Chrome on Mac.

I use Windows and I have no access to Mac, so I cannot show the issue in detail, I only have the following screenshots. These are screenshots from a frontend, loaded on Chrome on a Mac.

English (base language, correct version) - no honeypot field above the final checkbox is visible:

Russian ('“Your name” is a honeypot field):

Arabic (same “Your name” honeypot field).

Within the past month, when my client was reviewing the changes to the forms and testing them, the issue wasn’t there. Since then, no changes to the form were made.

All forms (in all 3 languages) were created in exactly the same way, and are used in the same way too. They are used as a global component.

Has anyone experienced this as well, and maybe knows what could be causing it/how to solve it?

To make sure the client can get form submissions, I have currently disabled the honeypot in forms in Russian and Arabic pages.

Thank you in advance for any help and assistance on this.

HI @karinavsl,

currently, I don’t see a honeypot field there (Did you remove it?).

If you enable it, and see it you should check which styles are overriding the default ones. This should give you the clue why this is happening.

If you have a staging website, where the honeypot field is visible, you can share a link.

Best regards,
Matej