microsoft / microsoft/pxt-microbit
[iPad] Hero banner carousel indicator dots are cut off in landscape mode after opening two or more pages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
On iPad landscape mode, the carousel indicator dots in the hero banner on the micro:bit homepage are partially cut off after opening two or more pages from the banner items.
Steps to reproduce the behavior:
- Navigate to https://makecode.microbit.org/beta on iPad landscape mode.
- In the hero banner, locate a carousel item that includes a Show Instructions button.
- Tap Show Instructions to open the page in a new tab.
- Repeat the above step to open two or more pages.
- Return to the homepage and observe the hero banner carousel.
Actual behavior
The hero banner carousel indicator dots are partially cut off in landscape mode after opening two or more pages.
Expected behavior
The hero banner carousel indicator dots should be fully visible and rendered correctly in landscape mode, regardless of how many pages have been opened.
Screen recording
https://github.com/user-attachments/assets/6e605ce9-d866-4e3a-8586-0c3f788334b2
Additional context
1.OS: iPad Pro 11 26.4.1
2.Browser: Safari
3.Makecode.microbit.org version: 8.1.12
4.Microsoft MakeCode version: 12.3.7
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 on the MakeCode micro:bit beta homepage in iPad landscape mode with Safari, following the listed steps for opening multiple Show Instructions pages. Then locate the hero banner carousel implementation and verify that the indicator dots remain fully visible after returning to the homepage; done means the dots are no longer cut off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100