-
Notifications
You must be signed in to change notification settings - Fork 301
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
Only navbar renders on iPhone #277
Comments
Seeing the same issue. Any movement? |
Any idea if this issue only happens with |
I've deployed this example using the dev version of flexdashboard here https://loving-dijkstra-7d4f33.netlify.app/ Do you only see the navbar at this link? If so, please include more info about your device and browser. |
@cpsievert I had the same issue but your link seems to work on my iPhone now. How did you solve the problem? I’m using safari. |
Weird. I just rendered this Rmd with the development version of flexdashboard https://github.com/cpsievert/flexdb-test/blob/gh-pages/index.Rmd Maybe updating to the development version will fix your problem? |
Hello @cpsievert ! The html file opens fine on PC/Chrome and on MacBook Chrome & Safari (full screen), and on android/Chrome (automatic vertical mobile layout), but on IPhone/Safari only the unclickable navbar shows (less the pages I'd normally see). This happens on old and new iPhones/OS. This error happens with no layout specified and with Adding Your linked development version from Mar 2021 on my iPhone shows properly.
@YSG-Jason @kvdwiele @jffni Did you find any workarounds apart from using the flexdashboard in dev? Worried about that in case it's not sustainable (such as a future relased package not including that fix, like now). |
Somehow flexdashboard doen't work on iPhone properly. Only navbar renders and nothing more. It works fine on Android and my PC, but not on iPhones.
This simple example:
Results in this on iPhone:
Is there a way to fix this?
I am using
flexdashboard 0.5.2
,rmarkdown 2.3
,R 4.0.2
and running on Windows 10 x64.Thanks.
The text was updated successfully, but these errors were encountered: