Page MenuHomePhabricator

Create popup with policy acknowledgement for when users register on the event page
Closed, ResolvedPublic2 Estimated Story Points

Description

As a campaign participant, I want to acknowledge the privacy policy and terms of use before registering for an event so I understand the legal guidelines that the event is under.

Prototype links:

Acceptance Criteria:

  • When the participant registers for the event, they must be able to acknowledge their approval of the terms of use and the privacy policy
  • The text should say: "By registering, you agree to the Terms of Use and Privacy Policy."
  • We do not need to include the greeting ("Hello Username!") for V0 and perhaps will not include it in later releases as well, depending on user feedback.

Visual example:

Screen Shot 2022-05-26 at 12.40.26 PM.png (1×2 px, 437 KB)

Event Timeline

ldelench_wmf set the point value for this task to 2.May 26 2022, 4:57 PM
ldelench_wmf moved this task from Backlog to Estimated/Ready for work on the Campaign-Tools board.
ldelench_wmf subscribed.

Added to sprint 15 per discussion at 2022-06-09 sprint planning.

Change 805847 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Display policy acknowledgement popup when registering for an event

https://gerrit.wikimedia.org/r/805847

Change 805847 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Display policy acknowledgement popup when registering for an event

https://gerrit.wikimedia.org/r/805847

A few comments on this ticket (which apply to T309334 as well) :

font-weight in the comp for the text By registering, you agree to the Terms of Use and Privacy Policy. is slightly lighter than it is in the build. If we change that to font-weight:300 then it matches the comp.

comp:

comp.png (182×652 px, 22 KB)

build:

build.png (176×666 px, 22 KB)


I am assuming we do not need a licensing policy link now since it is not in the AC, but since it is in the comp I wanted to mention it here.


Also @Daimona When I follow the QA testing notes T309334#8005531, and then click the terms of use and privacy policy links in the UI, the links open in the same window, but they should open in a new tab. When we have the Campaign Events extension and the terms of use and privacy policy on beta cluster, will we be able to have them open in a new tab? If so, is possible to test or recreate that on local currently?

A few comments on this ticket (which apply to T309334 as well) :

font-weight in the comp for the text By registering, you agree to the Terms of Use and Privacy Policy. is slightly lighter than it is in the build. If we change that to font-weight:300 then it matches the comp.

I think this could be a small difference due to using figma vs the actual OOUI component. In the code, we're using the standard message dialog component without changes.

Also @Daimona When I follow the QA testing notes T309334#8005531, and then click the terms of use and privacy policy links in the UI, the links open in the same window, but they should open in a new tab. When we have the Campaign Events extension and the terms of use and privacy policy on beta cluster, will we be able to have them open in a new tab? If so, is possible to test or recreate that on local currently?

I intentionally made it open in the same tab because it wasn't mentioned in the AC. I personally prefer links that open in the same tab, because you can get the other behaviour by middle-clicking / right-clicking / long-pressing, whereas if the link already opens in a new tab, it's not possible to force the other behaviour. That said, if this is something we should change, it would be a one-liner.

Also @Daimona When I follow the QA testing notes T309334#8005531, and then click the terms of use and privacy policy links in the UI, the links open in the same window, but they should open in a new tab. When we have the Campaign Events extension and the terms of use and privacy policy on beta cluster, will we be able to have them open in a new tab? If so, is possible to test or recreate that on local currently?

I intentionally made it open in the same tab because it wasn't mentioned in the AC. I personally prefer links that open in the same tab, because you can get the other behaviour by middle-clicking / right-clicking / long-pressing, whereas if the link already opens in a new tab, it's not possible to force the other behaviour. That said, if this is something we should change, it would be a one-liner.

Okay I see - I was going off of the figma interaction (which may be a default interaction for external links in figma?) and personal preference, but would be interested to see what @gonyeahialam thinks.

Also @Daimona When I follow the QA testing notes T309334#8005531, and then click the terms of use and privacy policy links in the UI, the links open in the same window, but they should open in a new tab. When we have the Campaign Events extension and the terms of use and privacy policy on beta cluster, will we be able to have them open in a new tab? If so, is possible to test or recreate that on local currently?

I intentionally made it open in the same tab because it wasn't mentioned in the AC. I personally prefer links that open in the same tab, because you can get the other behaviour by middle-clicking / right-clicking / long-pressing, whereas if the link already opens in a new tab, it's not possible to force the other behaviour. That said, if this is something we should change, it would be a one-liner.

Okay I see - I was going off of the figma interaction (which may be a default interaction for external links in figma?) and personal preference, but would be interested to see what @gonyeahialam thinks.

@vaughnwalters, @Daimona's suggestion seems to be the best solution in this context. Links open in the same tab, users can right-click if they want it in a new tab.

vyuen changed the task status from Open to In Progress.Aug 25 2022, 12:51 PM

The policy message is now displaying (see screenshot example), so I'm marking this as Done.

There are further enhancements we will make to the message, but these changes will be tackled in separate tickets.

Screen Shot 2022-09-23 at 5.01.40 PM.png (804×1 px, 135 KB)