#95282: "Tiles display incorrectly if the CSS "rotate" property is not supported"
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Gwiriit mar-plij ma n'eus ket dija un danevell evit an hevelep dodenn
M'oc'h a-du, VOTIT evit an danevell-mañ. An danevelloù gant ar muiañ a vouezhioù a vo studiet DA GENTAÑ !
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Deskrivadur dre ar munud
-
• Mar-plij, eilit/pegit ar gemennadenn fazi a zo war ho skramm, ma zo unan.
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
-
• Displegit deomp, mar-plij, ar pezh ho poa c'hoant d'ober, ar pezh ho peus graet hag ar pezh a zo c'hoarvezet 'benn ar fin
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Petra oa diskouezet war ar skramm pa 'z oc'h chomet stanket (Skramm goullo ? Ul lodenn eus etrefas ar c'hoari ? Kemennadenn fazi ?)
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Pesseurt reolenn n'eo ket doujet gant azasadenn ar c'hoari-mañ ?
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
-
• Ha posupl eo gwelet torridigezh ar reolenn e replay ar bartienn ? Ma 'z eo ya, da be niverenn taol ?
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Peseurt taol ho peus c'hoant c'hoari ?
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
-
• Petra emaoc'h o klask ober evit delankañ an ober c'hoari-mañ ?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Da be bazenn ar bartienn eo en em gavet ar gudenn (petra oa testenn kemenn ar c'hoari) ?
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
-
• What happened when you try to do a game action (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Mar-plij, diskrivit kudenn an diskwel. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
NOTE: This _might_ be the root cause of boardgamearena.com/bug?id=92210
# Problem
If the user's browser does not yet support the "rotate" property, then when placing tiles the image
will not rotate.
The game data gets updated with a rotation (0°, 90°, 180°, 270°) but the image will remain unrotated
(0°) hence it looks like the tile is not rotated; this improper feedback causes confusion and can even
caue improper placement (if they wrongly believe they have NOT rotated).
# The Fix
Simply adding the proper `transform:rotate()` lines, shown below, to these CSS classes will fix this
problem:
.sag_tile-rot-90 {
rotate: 90deg;
transform: rotate(90deg);
}
.sag_tile-rot-180 {
rotate: 180deg;
transform: rotate(180deg);
}
.sag_tile-rot-270 {
rotate: 270deg;
transform: rotate(270deg);
}
# Reference
Support for the rotate _attribute_ is barely 12 months old for many browsers.
See: developer.mozilla.org/en-US/docs/Web/CSS/rotate#browser_compatibility
And: developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotate#browser_compatibility
• Peseurt merdeer eo hoc'h hini ?
Google Chrome v103 and v115
Roll-istor an danevelloù bog
I tried this today, using BGA's CSS override option. It allowed me to rotate in an older version of chrome on an older mac that won't update chrome to the latest. It also allowed me to rotate on safari on my iPhone which is not on the latest annual update.
However, the rotation order was strange and would point up (single "1" blue tile with 1 blue arrow) when it should have been another orientation, as I cycled through the options. I committed the tile where it should have been automatically satisfied (pointing up to blue), but it didn't move the token. I then checked on a laptop with the latest macOS after removing the CSS override and see that the tile is not as it visually looked when I placed it (with the CSS override). So the visual and the actual were out of sync with just the addition of this code, at least using the common BGA CSS override in the profile.
Thanks for putting this out there in an attempt to correct what really needs to be implemented and tested directly into the game code.
Ouzhpennañ un dra bennak d'an danevell-mañ
- Niverenn taol all / Niverenn ar fiñv
- Ha renket eo bet ar gudenn gant an douchenn F5 ?
- Ha c'hoarvezet eo ar gudenn meur a wech ? Bewech ? Cheñch-dicheñch ?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
