MWPW-183392: Strikethrough price fix in express cards

[Axelcureno]

Fixes strikethrough issues in prices.

Resolves: MWPW-183392

Related Milo PR: adobecom/milo#5125

Test URL: https://main--mas--adobecom.aem.live/web-components/docs/express.html

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• b4ad68c ✅ (latest)
• e5c3ea1 ✅
• 4e0415a ✅

[honstar]

@Axelcureno, do you have a link on your branch where this can be tested? Is there an express card where the fixed styles can be verified somewhere in here: https://mwpw-183392--mas--adobecom.aem.live/studio.html#page=content&path=express

[afmicka]

@Axelcureno, do you have a link on your branch where this can be tested? Is there an express card where the fixed styles can be verified somewhere in here: https://mwpw-183392--mas--adobecom.aem.live/studio.html#page=content&path=express

@honstar the 4th fragment (link) in Express surface is a good candidate for checking the changes. Compare how any pricing fragment looks on https://main--mas--adobecom.aem.live/studio.html#page=content&path=express

or this one is even better example - https://mwpw-183392--mas--adobecom.aem.live/studio.html#page=content&path=express&query=59f7d2ba-82f4-4d71-baeb-c55bfd029ec6

You will see

vs

@Axelcureno please keep testing urls in the PR description (before and after). Do not remove them.
Also, could you please add an example to our testing mas gallery page - https://main--mas--adobecom.aem.live/web-components/docs/express.html. Update one of the fragments and adjust Nala if needed, please.

[honstar]

LGTM

[afmicka]

@Axelcureno strikethrough price color on full pricing Express fragment is not per figma, it is much darker.
It is fixed on simplified pricing. Though i am not confused what the colors should be because i see 2 different examples in figma

full pricing with your branch

simplified with your branch:

figma with both

confusing figma (we still have this combination on prod but is changed with this branch, not sure which one is correct):