After correcting the countdown on mobile version2
This commit is contained in:
parent
1d2aae29b4
commit
a8c0617591
@ -155,11 +155,14 @@ class _PredictionScreenState extends State<PredictionScreen> {
|
|||||||
children: [
|
children: [
|
||||||
Row(
|
Row(
|
||||||
children: [
|
children: [
|
||||||
_StatusChip(
|
// Web parity: `round.status` is already the authoritative,
|
||||||
round != null
|
// baked-in effective status (see `mergeRound` /
|
||||||
? serverAdjustedCountdown(round).effectiveStatus
|
// `_withEffectiveStatus`). Re-deriving it here from a second,
|
||||||
: 'waiting',
|
// independent `DateTime.now()` clock (out of sync with
|
||||||
),
|
// `_LiveCountdown`'s own ticking clock below) is exactly what
|
||||||
|
// caused the badge and the big countdown number to briefly
|
||||||
|
// disagree. Trust the single source of truth instead.
|
||||||
|
_StatusChip(round?.status ?? 'waiting'),
|
||||||
const Spacer(),
|
const Spacer(),
|
||||||
if (round != null)
|
if (round != null)
|
||||||
_LiveCountdown(
|
_LiveCountdown(
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user