#63937: "BUG - MOBILE - ANDROID - CHROME - Discard UI was placed under the playerboard one time"
どうしましたか?以下から選んでください
どうしましたか?以下から選んでください
同一内容の報告がないか、ご確認ください
もしそうなら、このレポートに投票してください。投票の多いレポートから調査されます!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
詳細
-
• もしあれば、画面に表示されたエラーメッセージをコピー&ペーストしてください
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. -
• 何をしたいか、何をしたか、何が起きたかを説明してください
n/a
• あなたのブラウザは何ですか?
Google Chrome v100
-
• あなたの言語の代わりに、表示されている英語の文章をコピー&ペーストしてください。 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. このテキストは翻訳ページで翻訳可能になっていますか?もしそうならば、24時間以上前に翻訳されていますか?
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
-
• 何を意味するのか、簡単に理解できるようにあなたの提案を正確かつ簡潔に説明してください。
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
-
• ブロックされたときの表示は何でしたか(空のスクリーン?一部のみのゲームインターフェイス?エラーメッセージ?)
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
-
• BGAで正しく実装されていないルールはどの部分ですか?
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. -
• ルールの間違いはゲームのリプレイで確認できますか?そうであれば、行動番号は何番ですか?
n/a
• あなたのブラウザは何ですか?
Google Chrome v100
-
• やりたかったゲームアクションは何ですか?
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. -
• このゲームアクションを引き起こす為に何を試みましたか?
n/a
-
• これを行おうとしたときに何が起こりましたか?(エラーメッセージ、ステータスバーメッセージ、他)
n/a
• あなたのブラウザは何ですか?
Google Chrome v100
-
• どの段階でこの問題が起こりましたか?(画面の指示はどうなっていましたか)
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. -
• ゲームアクションを行おうとしたとき、何が起こりましたか?(エラーメッセージ、ステータスバーメッセージ、他)
n/a
• あなたのブラウザは何ですか?
Google Chrome v100
-
• 表示の問題を説明してください 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.
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
-
• あなたの言語の代わりに、表示されている英語の文章をコピー&ペーストしてください。 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. このテキストは翻訳ページで翻訳可能になっていますか?もしそうならば、24時間以上前に翻訳されていますか?
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
-
• 何を意味するのか、簡単に理解できるようにあなたの提案を正確かつ簡潔に説明してください。
I had drawn too many cards, so the discard UI came up.
I was testing something else, so it had come up several times correctly. However, this time the z-sorting was wrong - most elements were above the scrim, and the cards in hand were below the playerboard.
i.imgur.com/nRwJ9Uu.png
I selected a card to discard and then triggered the discard UI again - and it looked fine. • あなたのブラウザは何ですか?
Google Chrome v100
報告履歴
Next steps would be to try to reproduce the bug with the chrome inspector open to see if any explicit error is thrown.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
報告に書き加える
- 他のテーブルID/行動ID
- F5キー(ページの再読込)で問題は解決されましたか?
- 問題は何回も起こりましたか?毎回 起こりますか?ランダムに起きますか?
- 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.
