NUKnightLab / NUKnightLab/TimelineJS3
Google Chrome Violations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
Hi Timeline-Team,
first of all: many thanks for the wonderful plugin.
I noticed that Google Chrome displays violations on pages with timeline on it.
The violations are visible in the console, when level is set to include »verbose«-messages.
One violation is e.g. the »readystatechange-handler« (see attached Screenshot).
It would be great to have these violation-warnings fixed in future releases.
Many thanks.
Best regards.
Christoph.
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 issue in Google Chrome with verbose console messages enabled on a page containing TimelineJS. Use the reported readystatechange-handler violation and attached screenshot as the starting point, then identify the source of each warning. Done means the reported Chrome violation warnings no longer appear in the console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100