#22599: "Display bug on Safari and small screens"
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Detaillierte Beschreibung
• Bitte beschreibe die Anzeigeschwierigkeiten. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
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.• Welchen Browser benutzt du?
Safari v13.1
Meldungshistorie
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.
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
Ergänze diese Meldung
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.