com.bloks.www.bloks.caa.reg.birthday, "What's your birthday?" — as the
fresh-install Android 453 app sends it (verified: the 453 sign-up
conformance scene, conformance.453/register-usa-number).
The accepted-password answer pushes it, so its enter sends nothing. The
person picks the day, month and year; submitBirthday sends
birthday.async and moves to the name screen. A birthday the server refuses
— an under-age one included — is the typed
RegistrationInvalidBirthdayError, and the modelled sign-up only supports the
18-and-over flow.
The 453 flow also renders an age-gating container inside this screen before
the date entry (the youth-regulation view the birthday step's answer
configures). It has no request of its own and no action the person takes
beside the date entry, so it is not a screen: its state is part of this
screen's reg_info bag and its view is the same frame.
No screenshot: the frame needs a registration that reached this step.
com.bloks.www.bloks.caa.reg.birthday, "What's your birthday?" — as the fresh-install Android 453 app sends it (verified: the 453 sign-up conformance scene,conformance.453/register-usa-number).The accepted-password answer pushes it, so its enter sends nothing. The person picks the day, month and year;
submitBirthdaysendsbirthday.asyncand moves to the name screen. A birthday the server refuses — an under-age one included — is the typedRegistrationInvalidBirthdayError, and the modelled sign-up only supports the 18-and-over flow.The 453 flow also renders an age-gating container inside this screen before the date entry (the youth-regulation view the birthday step's answer configures). It has no request of its own and no action the person takes beside the date entry, so it is not a screen: its state is part of this screen's
reg_infobag and its view is the same frame.No screenshot: the frame needs a registration that reached this step.