processing / processing/p5.js-web-editor
Loading Multiple HTML pages and CSS
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
Hi everybody,
I've used the p5.js online editor with my students for remote teaching during the covid19 period. And it's really a great tool that simplify programming learning! Thanks a lot all its developpers!
Teaching not only programming but also HTML/CSS, p5js editor is also very nice to create a first HTML/CSS page, to test it and publish it online. After having learned how to make an HTML page formatted with a .css file, we then create other HTML pages and a small website. So we've got a p5.js sketch into online editor with multiple web pages, all of them applying the same 'styles.css' styles :
https://editor.p5js.org/bardyl/present/J4ZS_c853
Nature of issue?
- Found a bug
Details about the bug:
- Web browser and version: Chrome Version 83.0.4103.116 (Build officiel) (64 bits)
- Operating System: Windows 10 Pro 64 bits
- Steps to reproduce this bug:
We have two problems:
-
when we click in the first html loaded page on a link to another web page of this mini website, the other HTML page loads in the browser BUT the 'styles.css' files is not applied to this second HTML page (even if apparently the browser loads it correctly). The problem is the same for all the other web page of the site/sketch. Chrome warns this problem in its console: "Resource interpreted as Stylesheet but transferred with MIME type text/html"
-
when running the sketch from editor or accessing to the mini website with the shared fullscreen link of the project, it's not the index.html page that is loaded (it's another HTML page, always the same one, but not the default
It would be great if we could use editor.p5js.org to also learn a little bit of HTML/CSS and make small sample mini website in order to learn these topics. That means, making little project with multiples HTML pages and css file applying to all of them.
Any idea? Thanks a lot for your precious input! 😃
Laurent
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the linked project in Chrome, checking index.html, the other HTML pages, and styles.css through the editor and fullscreen link. Compare the browser console and loaded resources when navigating between pages. Done means the default index.html loads first and styles.css is applied to every HTML page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100