All reports
medina_displayed reports
#43069: "On PC, the board is too large and goes behind the other white tabs below and chat."
fixed: Bug has been fixed
2
What is this report about?
What happened ? Please select from below
Display bug: some game information displayed was wrong (with no important consequence on the game)
Detailed description
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
On PC, the board is too large and goes behind the other white tabs below (how to play, leaderboards).
Another thing is the bottom right tower that covers the chat when the chat window is opened.
imgur.com/a/WoWSgXP• What is your browser?
Google Chrome v91
Report history
16. Jun 2021 17:33 •
ElNSTElN • Bug has not been reproduced by delopers yet:
18. Jun 2021 13:53 •
22. Jun 2021 21:37 •
22. Jun 2021 23:48 • I mentioned this already but I add it here as well. On Firefox browser in full screen the board is also too wide.
mindnektar • Bug has been fixed:
9. Sep 2022 9:32 • I just started my first game of Medina, and for me this is still happening. Browser is Chrome: i.ibb.co/FbydpK6/Screenshot-2022-09-09-at-09-28-36.png
No problem in the mobile app.
No problem in the mobile app.
paramesis • Bug has been fixed:
25. Sep 2022 16:32 •
27. Sep 2024 16:08 • I can confirm the issue is happening for me as well on Chrome/PC, similar screenshot as mindnektar
table boardgamearena.com/3/medina?table=302861783
There seems to be an issue with how the board-scale CSS property is defined.
If I uncheck both of these items below in devtools, it looks correct.
style attribute {
--board-scale: 1.46508;
}
:root {
--board-scale: 2;
}
table boardgamearena.com/3/medina?table=302861783
There seems to be an issue with how the board-scale CSS property is defined.
If I uncheck both of these items below in devtools, it looks correct.
style attribute {
--board-scale: 1.46508;
}
:root {
--board-scale: 2;
}
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.