Android Google chrome access shows no response.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
Information:
- Prism version: 1.29.0
- Plugins: line-numbers+show-language+toolbar+copy-to-clipboard
- Environment: Android Google Chrome
Description
Highlighted code blocks that are accessed more often with smart devices such as Android Google Chrome are not responding, and the following is a performance bottleneck for F12 viewing.
Example
Contributor guide
No contributing guide indexed for this repository
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
No source files or tests are identified in the report. Start by reproducing the unresponsive highlighted code blocks in Android Google Chrome with Prism 1.29.0 and the listed plugins, then trace the browser interaction and F12 performance behavior; done means the blocks respond and the reported bottleneck is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100