@W-16797872 Add Domain attribute to dw_dnt cookie

[jeremy-jung1]

Description

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

• (step1) Go to https://aaa-jeremy-wasatch-jeremy.mobify-storefront-staging.com/
• (step2) Open developer tools -> Application -> Cookies
• (step3) See that the cookie was created with the Domain, .aaa-jeremy-wasatch-jeremy.mobify-storefront-staging.com. The leading dot indicate that the cookie will be accessible to subdomains of this hostname.
• (step4) Compare this to the dw_dnt cookie being created in https://runtime-admin-n16.mobify-storefront.com/, which does not have the leading dot. Click out of the form to have the cookie be created.

The usage of the hook in the UI after this change, to enable subdomain in PWA kit for the DNT cookie is:

// use-dnt-notification.js
const [hostname, setHostname] = useState(undefined)
const {dntStatus, updateDNT} = useDNT(hostname)

useEffect( () => {
        if (window.location.hostname) {
            setHostname(window.location.hostname)
        }
}, [])

const onCloseNotification = () => {
        updateDNT(null, hostname)
        onClose()
}
const onClickAccept = () => {
        updateDNT(true, hostname)
        onClose()
}
const onClickDeny = () => {
        updateDNT(false, hostname)
        onClose()
}

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[vcua-mobify]

We might want to test this change on a hybrid environment and ensure that the dw_dnt cookies created in PWA work in SFRA with the domain (they probably do, but it might be good to just make sure). Also do we want to check for the case where the dw_dnt cookie is created in SFRA?

[jeremy-jung1]

This feature is a nice-to-have and won't be released before the holidays, and taking into Hybrid support will need some more discussion, as in SFRA the domain is hardcoded in ECOM. This means that if PWA kit is using a subdomain and SFRA isn't, then the cookie coming from SFRA into PWA kit will not be read by PWA kit, resulting in a total of two cookies in the browser.