-
Notifications
You must be signed in to change notification settings - Fork 35
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
Update/Assess javascript resources #12
Comments
we will enter validation steps with the settled javascript sources:
|
rkrenn
added a commit
that referenced
this issue
Jun 30, 2022
rkrenn
added a commit
that referenced
this issue
Sep 27, 2022
rkrenn
added a commit
that referenced
this issue
Oct 19, 2022
rkrenn
added a commit
that referenced
this issue
Nov 4, 2022
rkrenn
added a commit
that referenced
this issue
Nov 4, 2022
rkrenn
added a commit
that referenced
this issue
Feb 15, 2023
rkrenn
added a commit
that referenced
this issue
Feb 16, 2023
rkrenn
added a commit
that referenced
this issue
Feb 23, 2023
rkrenn
added a commit
that referenced
this issue
Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some javascript resources are not up to date, which could mean that there compatiblity with new browsers might be a problem.
It would be helpful to minimize the usage of third party libraries (~software of unknown provenance). A javascript audit would be a good starting point. For corner cases, where a small feature might introduce a lot of javascript code the necessity of the features needs to be thoroughly reasoned.
The text was updated successfully, but these errors were encountered: