New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discount code bugs #19593
Discount code bugs #19593
Conversation
e4a2ee2
to
563d18a
Compare
@@ -144,11 +153,11 @@ export default class EligibilityChecklist extends Component { | |||
According to our data, your school has fewer than 50% of students that are | |||
eligible for free/reduced-price lunches. This means that we can bring down | |||
the cost of the $325 kit to just $97.50.{" "} | |||
<b> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with removing {b} but would it be possible to use {strong} rather than {div} here? Screenreaders are able to emphasize the strong tag, so it become perceivable by folks using screenreaders.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fwiw, the reason i removed the b is because for whatever reason, just bolding gotham 4r seemed to show very little difference in bold. i saw that we use gotham 7r where we want bold elsewhere, so switched to that.
will add a strong. thx for the pointer :)
@@ -129,7 +133,7 @@ export default class EligibilityConfirmDialog extends Component { | |||
<label> | |||
<div>{i18n.verifySignature()}</div> | |||
<div style={styles.signature}> | |||
<b>Electronic Signature</b> {i18n.typeName()} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment re: {strong}
This PR fixes a bunch of small bugs we discovered while walking through the discount code flow on staging-next.
fullDiscount
for some reason when passing to instructionsonClick
was still fired. This fixes that.