-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Slides shifted to the right in the webapp #67
Comments
I'm not really sure if there's something wrong with my environment or if it is hardware related. I don't really know much about frontend development. I initially thought the culprit was my external monitor (although it has the same form factor as the MacBook's display) but this happens even with the external monitor disconnected. The exported PDF is also shifted in the same direction (BTW, the latex is not correctly rendered in the exported PDF). |
Can't reproduce on my side. Can you check the consoles, and inspect the dom to see what's wrong? Thanks |
I have the same issue. Reproduction is here. May-12-2021.05-01-23.mp4I can fix it by removing the "margin: auto" from "#slide-content", but... |
Hi, I think it can be solved by removing the width of "slide-content" : |
Sorry but what? 😂 Looks like it's redundant, and we could remove it and push a fix |
Released in 0.7.4. Would be appreciated if you can help verify if it works. |
Thanks. It has been fixed. |
Thanks @antfu! It's 100% fixed on my setup, and working on different screens and resolutions. |
Hello! Great project. I've been using markdown to write beamer slides for years (with
pandoc
) and this is a really nice addition to that space.One small issue I've been having is that when I open the web app, my slides seem to be all shifted to the right.
Steps to reproduce
These are the steps I used:
npm init slidev
and follow all standard options. Wait for all packages to be installed.http://localhost:3030
.The slides open like this:
![image](https://user-images.githubusercontent.com/126856/117867073-40e79e80-b26e-11eb-8b8a-15d7c39a4735.png)
The text was updated successfully, but these errors were encountered: