Does anyone know why you can see text reading “adobe-font-something” behind my navbar?
Adobe fonts are installed on the site but obviously the user shouldn’t be seeing any mention of it.
Here is my site Read-Only:
Does anyone know why you can see text reading “adobe-font-something” behind my navbar?
Adobe fonts are installed on the site but obviously the user shouldn’t be seeing any mention of it.
Here is my site Read-Only:
Hi there,
While this specific issue with Adobe fonts appearing behind the navbar isn’t directly covered in our documentation, here are some troubleshooting steps you can try:
Check your navbar’s z-index property in the Style panel to ensure it’s higher than other elements on the page. A higher z-index value will keep the navbar in front of other elements. You may also want to verify that the navbar’s position is set to “relative,” “fixed,” or “absolute” for the z-index to take effect.
If the issue persists, inspect the Adobe font container’s positioning and z-index values. Sometimes, text elements can have unexpected stacking behavior due to their parent container’s properties.
Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.
Thanks! The thing is, I haven’t placed the text in the website, I think it’s possibly pulling from the Adobe font api?
So none of the troubleshooting suggestions will make a difference, as there isn’t a text element physically on the pages if that makes sense.
Hopefully someone from the community can help
I know that Adobe’s documentation states “To use these fonts on a web page, copy this code into the <head>
tag of your HTML”
but with Webflow’s integration, you do not need this step. Did you add this code?
Hi Rachel,
Since it’s happening on every page, check your site-wide head and body code. It looks like you have the plain text Adobe-font-script
somewhere outside of your script elements.
It is not being generated by JavaScript.
Hey Michael, thanks so much for your response (and sorry I’m so late on getting back to you!) I found the text that was causing the issue, so that’s it sorted. Thanks for your help!