#45999 closed feature request (fixed)
Remove privacy pointers again
| Reported by: | garrett-eclipse | Owned by: | desrosj |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.2 |
| Component: | Privacy | Version: | 4.9.6 |
| Severity: | normal | Keywords: | has-patch commit |
| Cc: | Focuses: |
Description
This ticket is to trac the discussion on timeline for removing the wp496_privacy pointer.
As @desrosj indicated we'll need to look historically how long pointers lifespans have been and decide upon a timeline and release for deprecating the Privacy pointer.
Reference - https://core.trac.wordpress.org/ticket/45529#comment:11
As 5.1 RC is impending I would assume this would be 5.2+ unless it becomes a blessed task (leaving that decision to others..
Attachments (1)
Change History (14)
#2
@
7 years ago
- Severity blocker → normal
- Summary Ticket for removal of the Privacy Pointer in a future release → Remove privacy pointers again
This ticket was mentioned in Slack in #core-privacy by garrett-eclipse. View the logs.
7 years ago
This ticket was mentioned in Slack in #core-privacy by garrett-eclipse. View the logs.
7 years ago
This ticket was mentioned in Slack in #core-privacy by desrosj. View the logs.
7 years ago
#7
@
7 years ago
- Keywords 2nd-opinion dev-feedback removed
- Milestone Future Release → 5.2
- Owner set to
- Status new → assigned
Let's remove this in 5.2. There are a few issues with the implementation (#44136), and 5.2 will be the third major release after the feature was introduced in 4.9.6.
This ticket was mentioned in Slack in #core-privacy by desrosj. View the logs.
7 years ago
#9
@
7 years ago
- Keywords has-patch needs-testing added; needs-patch removed
45999.diff removes the privacy pointer added in 4.9.6.
#10
@
7 years ago
Looks fine to me @desrosj , I just want to add that when we implemented these pointers we've added a small css addition as well https://core.trac.wordpress.org/attachment/ticket/43942/43942.3.diff at src/wp-includes/css/wp-pointer.css.
I'm guessing that stays though as an overall addition, correct?
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
IMHO Privacy Pointer is very nagging for users in backend.
In general is very nagging as well for all other usages in backend.
I suggest to totally remove it for all usages!