Sorry, another idea to deal with "cross-site cookies" not being super intuitive for users, how about: **Allow amazonpay.com to track you on this site?** > amazonpay.com is requesting access to cross-site cookies that can be used to track what you do on oldnavy.com. You may want to block access if it's not clear why this data is needed. Also, while we're bikeshedding, I wonder how much this sentence really helps: > You may want to block access if it's not clear why this data is needed. Maybe we could refactor it to > You should block access if you're not familiar with amazonpay.com Since the requesting party should have introduced itself in-content in some way. Thoughts?
Bug 1706425 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry, another idea to deal with "cross-site cookies" not being super intuitive for users, how about: ---------------------------------------------------------- **Allow amazonpay.com to track you on this site?** > amazonpay.com is requesting access to cross-site cookies that can be used to track what you do on oldnavy.com. You may want to block access if it's not clear why this data is needed. ---------------------------------------------------------- Also, while we're bikeshedding, I wonder how much this sentence really helps: > You may want to block access if it's not clear why this data is needed. Maybe we could refactor it to > You should block access if you're not familiar with amazonpay.com Since the requesting party should have introduced itself in-content in some way. Thoughts?
Sorry, another idea to deal with "cross-site cookies" not being super intuitive for users, how about: ---------------------------------------------------------- > **Allow amazonpay.com to track you on this site?** > amazonpay.com is requesting access to cross-site cookies that can be used to track what you do on oldnavy.com. You may want to block access if it's not clear why this data is needed. ---------------------------------------------------------- Also, while we're bikeshedding, I wonder how much this sentence really helps: > You may want to block access if it's not clear why this data is needed. Maybe we could refactor it to > You should block access if you're not familiar with amazonpay.com Since the requesting party should have introduced itself in-content in some way. Thoughts?