Skip to content

when running fullscreen mode the canvas is compressed to a thin squashed band #1938

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

Closed
lee2sman opened this issue Oct 7, 2021 · 5 comments · Fixed by #1940
Closed

when running fullscreen mode the canvas is compressed to a thin squashed band #1938

lee2sman opened this issue Oct 7, 2021 · 5 comments · Fixed by #1940

Comments

@lee2sman
Copy link

lee2sman commented Oct 7, 2021

Nature of issue?

  • Found a bug

Details about the bug:

  • Web browser and version: Tested on Chrome 94.0.4606.81 and Firefox 92
  • Operating System: Ubuntu Linux and Windows 10
  • Steps to reproduce this bug:

When you are logged in and Share > Present Mode, the new fullscreen opens up but the canvas is squashed so that it's about 100pixels high and as wide as your window. You can scroll through this squashed canvas. I believe this is new behavior but I don't know definitively. I don't see any errors on the console when this happens. Tested with multiple sketches.

@prabalp
Copy link

prabalp commented Oct 8, 2021

it's Share>Fullscreen, working fine for Share> Present Mode
Present: https://preview.p5js.org/Prabal/present/yh9ovX6dH
FullScreen: https://editor.p5js.org/Prabal/full/yh9ovX6dH

@catarak
Copy link
Member

catarak commented Oct 8, 2021

Thanks for reporting! I can reproduce. I recently unified some CSS and thought I tested it, but clearly I didn't do a good enough job 😄

@prabalp
Copy link

prabalp commented Oct 8, 2021 via email

catarak added a commit that referenced this issue Oct 8, 2021
@catarak
Copy link
Member

catarak commented Oct 8, 2021

I just did a hotfix release (v2.1.1) as this is an issue that affects all sketches, so this should be fixed once the application is built and deployed (~10 min from now).

@lee2sman
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants