"Read more about it" does nothing if you reached the home page from inside the site
A pull request for this has already been merged.
- #76 by @CakeRepository — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, javascript
Research direction
Start in web/app.js at aboutText() and the view-building logic near line 3884, then compare the About markup included by web/home.html. Reproduce by entering from /worlds or /world/commons before opening More > About and clicking “Read more about it.” Done means that action expands the panel to the full About text from both direct and in-site navigation paths.
Written by the indexing model from the issue text.
Description
What happened
Opening About on the home page after arriving by a link inside the site shows two lines and a Read more about it link. Clicking that link adds #about to the address and nothing else happens. The panel stays the same.
I expected the full About text, which is what you get when the home page is the first page you open.
aboutText() at web/app.js:468 only has the full text if the page was first loaded at /, because only web/home.html includes it. The comment above it says other pages link there "with a real page load". That's true from /worlds, but once you're already on /, a link to /#about is a jump within the page, so nothing reloads. The check that opens the panel at web/app.js:3884 only runs when the view is built.
Where
The About panel on the home page
How to see it again
- Open https://agentshangout.com/worlds directly.
- Click Back to The Commons.
- Click More, then About.
- Click Read more about it.
The address becomes /#about and the panel doesn't change. It's the same from /world/commons through More, then Home.
Seen on agentshangout.com on 2026-10-31, signed out.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from CakeRepository/agentshangout
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
CakeRepository/agentshangout#294 ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
CakeRepository/agentshangout#270 ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
CakeRepository/agentshangout#267 ·
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
CakeRepository/agentshangout#265 ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
CakeRepository/agentshangout#264 ·
All issues in CakeRepository/agentshangout
Similar issues
-
docs(metrics): replace stale src/metrics.rs line anchors in dashboard-metrics.md with symbol namesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
ci-cd desktop size:low telemetry-improvement telemetry-round-1
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vfarcic/dot-agent-deck#2079 ·
Maintainers usually reply within 1 day
-
enhancement user-priority/P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days