Line Annotations do not position correctly on Edge
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- frontend
Research direction
No file, test, or entry point is named. Start by reproducing the line-annotation positioning problem in Microsoft Edge using the 2.8 interface, then inspect the relevant frontend entry point. Done means line annotations are positioned correctly in that interface without introducing regressions.
Written by the indexing model from the issue text.
Description
Only in the 2.8 interface. There may be other things to discover.
- Dominant language
- Java
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from CenterForDigitalHumanities/TPEN28
-
bug IIIF interoperability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
interoperability
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
interoperability
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
interoperability
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CenterForDigitalHumanities/TPEN28
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
[Bug]: REST API URL starting with "http" but no scheme (e.g. httpbin.org/get) is not given an http:// prefixPossibly taken @ItsDeadlyProgrammer claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
appsmithorg/appsmith#42471 · 1 comment ·
Maintainers usually reply within 2 days
-
code-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
bug priority: medium Review effort [1-5]: 3 status: needs-triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
carlos-emr/carlos#5258 ·
Maintainers usually reply within 1 day