-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Radcliffe 2: contact information not displaying on mobile #7755
Comments
Support References This comment is automatically generated. Please do not edit it.
|
8061784-zd-a8c |
📌 REPRODUCTION RESULTS
📌 FINDINGS/SCREENSHOTS/VIDEOReplicated. This is how to see how to test this and the effect it has. Screen.Capture.on.2024-04-24.at.21-45-44.mov📌 ACTIONSTriaged |
This theme is quite old, but from what I remember the expected behaviour is to minimize the contact info to the icon only on mobile (tapping the icon performs associated action - open maps, open email app, or call). I tried it just now, and it is indeed how it worked for me (and this is how the demo site behaves too) These icons (without the associated text) is the expected bahavior on mobile: But the video from @rickmgithub doesn't have the icons - do you have a link to that site or can you still replicate so that I can investigate more? |
Duplicate of #7711 - svg icons being hidden, already fixed by @miksansegundo #7711 (comment) |
Quick summary
On sites with the Radcliffe 2 theme active, contact information does not appear on the header on mobile devices.
Steps to reproduce
What you expected to happen
Contact information should appear at the top of the site header, like it does on the desktop.
What actually happened
Contact information is not showing.
Browser
No response
Context
Customer report: 8068856-zen
Platform (Simple, Atomic, or both?)
Simple
Other notes
Might be related to this other issue: #7744
8068856-zen reported both issues together.
Reproducibility
Consistent
Severity
All
Available workarounds?
None
Workaround details
No response
The text was updated successfully, but these errors were encountered: