Safari browser, when clicking on the login button, loads an unknown file.
This is reproducible for a very small number of users.
I cannot reproduce this.
I suspect that these users have an old Mac OS.
Here is my button
I was looking for a solution and found a tip that Safari can catch a click on an svg and load it,
I put pointer-events: none; for svg
but it didn’t work
.login-button svg {
pointer-events: none;
}
Hey @OksanaR - thanks for posting in the Community!
To ensure we get you the best support possible, can you please provide more context regarding the “login” button in question? Specifically, are you referencing the login button to your HubSpot portal? Any additional context you can provide will be helpful to solving for the issue!
Shane, Senior Community Moderator
Hi @STierney , thanks for your reply!
This is not the HubSpot portal login button.
It’s a custom login button on our public website, built using HubSpot CMS (custom module).
The button links to our external product login page (e.g. TransferRoom).
For a very small number of users using Safari on older macOS versions, clicking the button does not redirect.
Instead, Safari attempts to download an empty/unknown file.
The issue is not reproducible on modern Safari versions and does not occur in Chrome or Firefox.
The link is configured as a standard URL link field in the module (not File).
The button contains inline SVG markup.
Hey @OksanaR - thanks so much for providing this follow-up context!
I’d like to tag in a few Community experts here to see what insight they may have for us on this behavior. @Anton, @jeremymandle, and @alyssamwilie - any thoughts on why users may be experiencing this issue when using Safari on older macOS versions?
Shane, Senior Community Moderator
found this old Reddit topic where users experiencing the same issue and provide a fix. But since this isn’t a code fix, it’s something I’d use for something like a knowledge base/tipp.
Since you’re using the URL field in the module, your HubL should look like this:
{{ module.login_link.url.href }}
(this might also solve the problem)
Furthermore - since it’s unlikely that the login page will change frequently, you can use a text field(not rich-text) as URL.
In this case, the HubL (assuming you’d call it “Login link”) would look like this:
Hi @Anton , thanks a lot for the tip and for digging up that Reddit thread! I’ll try the fix mentioned in the article first, and then I’ll look into your suggestions regarding the HubL field.
Really appreciate the help!