[wp-trac] [WordPress Trac] #44677: Verbiage for Copy in Privacy Guide should be more explicit

[WordPress Trac]

#44677: Verbiage for Copy in Privacy Guide should be more explicit
----------------------------------------------+----------------------------
 Reporter:  garrett-eclipse                   |       Owner:  garrett-
                                              |  eclipse
     Type:  enhancement                       |      Status:  accepted
 Priority:  normal                            |   Milestone:  5.1
Component:  Privacy                           |     Version:  4.9.6
 Severity:  normal                            |  Resolution:
 Keywords:  has-screenshots has-patch commit  |     Focuses:  privacy
----------------------------------------------+----------------------------
Changes (by garrett-eclipse):

 * keywords:  has-screenshots ui-feedback ux-feedback has-patch needs-design
     => has-screenshots has-patch commit
 * status:  assigned => accepted
 * milestone:  5.2 => 5.1


Comment:

 Thanks @JoshuaWold I appreciate you taking the time to look at this.

 Replying to [comment:15 JoshuaWold]:
 > This ticket is only asking what that button should say. The use case
 (I'm assuming) is that a user might want to copy the entire privacy policy
 for sharing elsewhere.
 Just to clarify the primary use case is to copy the suggested text to be
 used on your Privacy Policy page. So a user would copy the content and
 paste it into their Privacy Policy. By default on a clean install the
 Privacy Policy page is filled with this suggested text, so the guide is
 more for reference and for legacy users or users with pre-existing Privacy
 Policy pages.

 As well when the policy verbiage changes or new plugins add additional
 suggested text then the user would get a notice and find additional
 sections on their guide. Each section would be copiable separately so you
 can get just the portion you need.

 Replying to [comment:15 JoshuaWold]:
 > In future releases I might suggest just taking the button out, as it
 could add more confusion than help. For instance, users not knowing where
 they're supposed to paste it from, and the fact that I can easily select
 the text on my own and copy it.
 One hesitation I have with removing the button entirely is the content
 copied isn't exactly everything that's displayed. Inline with the
 suggested text for each section is some surrounding context information
 which shouldn't be carried over to the Privacy Policy page as such the
 Copy button is preferred over the manual copy as you'd copy only the
 desired text and not accidentally select any of the context information.

 As an example of this Under the Media section there's the context
 information and then the suggested text;
 > **Media**[[BR]]
 > In this subsection you should note what information may be disclosed by
 users who can upload media files. All uploaded files are usually publicly
 accessible.
 >
 > Suggested text: If you upload images to the website, you should avoid
 uploading images with embedded location data (EXIF GPS) included. Visitors
 to the website can download and extract any location data from images on
 the website.
 In the above example the Copy button will capture the 'Media' heading and
 the suggested text but avoid the portion inbetween them.

 If a user were to manually copy the text they wouldn't be able to capture
 just the suggested text as often the context information is inbetween
 portions of the suggested text.

 As such I'm not going to bother opening a new ticket to investigate the
 removal of the Copy button as I feel it necessary due to the context text
 which we don't want to copy.

 Replying to [comment:15 JoshuaWold]:
 > **Given that, and given the discussion in this ticket already, I agree
 with changing the copy to:**
 >
 > **"Copy this section to clipboard"**
 >
 > It's wordy, but it's the most explicit, and we want to make sure we're
 clear on what this tool is for.
 >
 > Hope that helps, thanks everyone!
 THANK YOU for the review/feedback and approval, as this is a small
 verbiage change and is ready I'm going to move it to 5.1 and mark for
 commit to see if we can slide it into that RC.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44677#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform