Issues with glossaries
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- frontend
Research direction
The payload names no files or tests, so start by reproducing in the lesson page: click an underlined glossary term in rich text and watch how the page scroll changes. Find the code that handles the term click and positions the glossary popup, then check whether it uses the clicked word's position or a fixed offset. Done means the popup opens next to the clicked word at any screen size, does not move the scroll, and shows highlighted code.
Written by the indexing model from the issue text.
Description
There are some situations remaining where glossary entries bug, like they change the scrolling and don't show up.
I don't know if it's an interaction between the global page scroll and the glossary, or what is happening exactly, but this needs investigation.
Another issue is that the glossary placement still is sometimes off.
To do:
- Verify if there is any place in the application where we store a different scroll anything in the lesson and the glossary pop ups interacts with scrolling.
- Figure out why, in some situations but not others, clicking an underlined term in the rich text label changes scrolling.
- Ensure that the positioning of glossary entries is reliable and based on clicked word position.
Also, the glossary pop ups do not work well at large screen sizes. We should make sure that they have more width based on the application content scale/zoom level + a fallback scroll container probably.
Last but not least, code is not highlighted anymore inside glossary pop ups.
- Dominant language
- GDScript
- Stars
- 2.8k
- Forks
- 236
- 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 GDQuest/learn-gdscript
-
user experience
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
GDQuest/learn-gdscript#1438 ·
-
user experience
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
GDQuest/learn-gdscript#1420 ·
-
user experience
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
GDQuest/learn-gdscript#1437 ·
-
user experience
Difficulty 5/5 Over a week Newbie friendliness 12/100
GDQuest/learn-gdscript#1436 ·
-
Practices syntax highlighting: Certain types like String and Vector2 are not highlightedMay be free again A pull request for this issue was closed without being merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
GDQuest/learn-gdscript#1434 ·
All issues in GDQuest/learn-gdscript
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Agenta-AI/agenta#7542 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Harden bayesian-waves-bg.js: add prefers-reduced-motion, pointer-events guard, and hidden-tab pauseOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
njitacm/njit-acm-website#110 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100