Skip to content
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

Changes in text position #1473

Closed
Hemant2A2 opened this issue Dec 22, 2023 · 5 comments
Closed

Changes in text position #1473

Hemant2A2 opened this issue Dec 22, 2023 · 5 comments
Labels

Comments

@Hemant2A2
Copy link
Contributor

Most appropriate sections of the p5.js website?

Reference

What is your operating system?

Mac OS

Web browser and version

Chrome , Version 120.0.6099.109 (Official Build) (arm64)

Actual Behavior

Screenshot 2023-12-22 at 1 28 26 PM Screenshot 2023-12-22 at 1 29 48 PM
  1. In the first image there is a huge gap between normal() and vertexNormal().
  2. In the second image p5.FrameBuffer is out of the column.

Expected Behavior

  1. Gap should be removed.
  2. p5.FrameBuffer should be put inside the column.

Steps to reproduce

Go to : https://p5js.org/reference/ , scroll down and look for Vertex and Rendering column

Would you like to work on the issue?

Yes , I would like to work on this issue

@Hemant2A2 Hemant2A2 added the Bug label Dec 22, 2023
@limzykenneth
Copy link
Member

This is due to the way the inline reference is used to generate the data file. There might not be a strightforward way to solve this and related to #1452, it may not be worth the effort to solve it now instead of waiting for the new version of the website to be done.

@shardulgawande27
Copy link

@limzykenneth I want to solve this issue, the ejs in list.html tml looks fine. But the backend is getting overwhelming because am unable to find as in how the whole is being sent to the frontend

@limzykenneth
Copy link
Member

@shardulgawande27 Thanks for the interest however per #1452, we are not currently looking to fix this as there are a new website currently in the pipeline. I'll close this issue for now.

@shardulgawande27
Copy link

@limzykenneth no problem. Actually I had previously worked on this issue of sister navigation #1495, would like to contribute to new processing website that is currently in the pipeline if allowed to do so.

@limzykenneth
Copy link
Member

We are currently working with designers and developers on creating the new website and are not looking for additional contributors at the moment. Thanks.

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

No branches or pull requests

3 participants