[wp-trac] [WordPress Trac] #43895: Organize privacy functions into logical files and classes

[WordPress Trac]

#43895: Organize privacy functions into logical files and classes
-------------------------------------------+-----------------------
 Reporter:  iandunn                        |       Owner:  desrosj
     Type:  enhancement                    |      Status:  assigned
 Priority:  normal                         |   Milestone:  5.3
Component:  Privacy                        |     Version:  4.9.6
 Severity:  normal                         |  Resolution:
 Keywords:  early has-patch needs-testing  |     Focuses:
-------------------------------------------+-----------------------

Comment (by azaozz):

 > Should the CSS for privacy tools and guide be isolated to their own .css
 files

 Good question. The only stand-alone file that may need that is (the new)
 `privacy-policy-guide.php`. The other screens are part of "settings" which
 is (mostly) `forms.css` and list tables in `list-tables.css`.

 It will perhaps make sense to move the CSS for the privacy policy guide
 out of edit.css to a separate file. On the other hand it's just a few
 lines, maybe better to leave it as-is or to add it to `common.css`?

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