All reports
Thurn and Taxis reports
#22599: "Display bug on Safari and small screens"
What is this report about?
What happened? Please select from below
Display bug: some game information displayed was wrong (with no important consequences for 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.
The cards don't quite display correctly on iPhone, or on Safari on MacOS if the size of the window is small. imgur.com/a/HUExtQT
The same issue affects the display of collected bonus tokens, although not the ones on the board.• Which browser are you using?
Safari v13.1
Report history
Aug 14th 2020 1:08 • shadowphiar • Bug has not been reproduced by developers yet:
Fortunately these cards have enough of a border that it doesn't really interrupt the game, but this will work better if background-position is specified in terms of offsets in px instead of percentages of the card size.
Sadly Safari handles background-position slightly differently to other browsers when it is specified as a percentage (that is, a multiple of the size of the object being displayed). After calculating the size of the box being displayed, Safari appears to truncate/round those dimensions to an integer number of pixels as they are displayed on the screen, and then draw the image offset by percentages of that integer value. This becomes significant in small windows because the whole view gets scaled down so as to fit the minimum width. This difference of up to half-a-pixel, multiplied by percentages like 2200% adds up to an offset that can be substantial.
NB: I'm not saying Safari isn't wrong to be doing this truncation, but even if someone gets them to fix it, then it will still only look right for BGA users who have updated to the latest and greatest Safari version, whereas using px offsets should be correct for all viewers.
Sadly Safari handles background-position slightly differently to other browsers when it is specified as a percentage (that is, a multiple of the size of the object being displayed). After calculating the size of the box being displayed, Safari appears to truncate/round those dimensions to an integer number of pixels as they are displayed on the screen, and then draw the image offset by percentages of that integer value. This becomes significant in small windows because the whole view gets scaled down so as to fit the minimum width. This difference of up to half-a-pixel, multiplied by percentages like 2200% adds up to an offset that can be substantial.
NB: I'm not saying Safari isn't wrong to be doing this truncation, but even if someone gets them to fix it, then it will still only look right for BGA users who have updated to the latest and greatest Safari version, whereas using px offsets should be correct for all viewers.
Aug 14th 2020 7:54 • Volker78 • Bug has been confirmed by developers:
Oh, that is ugly. One problem possibly: the background-size is bigger than required for being able to zoom without pixelating. The admins from BGA told me, to do it this way. The default BGA stock component (used for all card games) uses percentage positioning. I will ask them, how they plan to handle this problem.
Aug 18th 2020 19:12 • Volker78 • Bug has been confirmed by developers:
Could you please try again? I changed some bits..
If it will not work. Could you perhaps play a little bit with the background-size-settings? I now have set them fixed:
#carriages .stockitem {
background-size: 780px 100px;
}
and
.citycard {
background-size: 2300px 156px;
}
I am quite sure, it should have to do with the background-size. You could also try for the city cards
.citycard {
background-size: 3450px 235px;
}
and also adapt the stockitem html-fixed-size to 150px x 235 px
If it will not work. Could you perhaps play a little bit with the background-size-settings? I now have set them fixed:
#carriages .stockitem {
background-size: 780px 100px;
}
and
.citycard {
background-size: 2300px 156px;
}
I am quite sure, it should have to do with the background-size. You could also try for the city cards
.citycard {
background-size: 3450px 235px;
}
and also adapt the stockitem html-fixed-size to 150px x 235 px
Add to this report
Please add here anything that seems relevant in order to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? 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.
