This would let you close a banner but get another poke sooner than you would with the normal close button (which currently keeps us at bay for a full 7 days).
Description
Details
Event Timeline
Hey @AndyRussG, @Pcoombe & @atgo
Thanks for looking into this. Bummer there's not an easy way to do this in the banner, we thought there would be a simple solution to test it out. Do you have an idea if this would be a significant amount of work? We would like to use it for a test, but I think it might actually be something we would roll out across the campaign. We're getting a lot of banner closes and I think (but don't know for sure how many) of those closes are from people who were busy but who might want to donate later. It could be good for us to be able to better hide banners from people who really don't want to donate and still give a chance to those who do want to donate. If this is the type of thing that could break a bunch on stuff in central notice, let's hold off :) Thanks for your input!
Hi! On the contrary, it would be quick, simple and safe, I think! We're already planning a small deploy (to make the 'namespace' hide reason handled by banner history minification) so that could potentially go out at the same time...
Change 256615 had a related patch set uploaded (by AndyRussG):
ext.centralNotice.display: Add API for custom hide cookie reasons and durations
With this patch, we have a hard-coded 1-month limit to the duration of custom hide cookies, just as a precaution against cookie proliferation.
Change 256615 merged by jenkins-bot:
ext.centralNotice.display: Add API for custom hide cookie reasons and durations
Change 256863 had a related patch set uploaded (by AndyRussG):
ext.centralNotice.display: Add API for custom hide cookie reasons and durations
Change 256863 merged by jenkins-bot:
ext.centralNotice.display: Add API for custom hide cookie reasons and durations