WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #35395, comment 36


Ignore:
Timestamp:
09/23/2016 09:59:43 PM (3 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35395, comment 36

    v2 v3  
    1313Apart from the above there are several other things that are pretty bad:
    1414- Inadequate space for editing/writing. Try resizing your coding (text) editor to 275px width and edit something for 10-15 min. It's really bad.
    15 - "Deceiving" preview. CSS hacks affect the whole site but the user can see only one template in the preview. It is pretty easy to make a change that "looks good" on the front page but breaks the archive pages, etc.
     15- "Deceiving" preview. CSS hacks affect the whole site but the user can see only one template in the preview. For example it is pretty easy to make a change that "looks good" on the front page but breaks the archive pages, etc.
    1616
    1717In addition there is no good way to make the user entered CSS "secure". CSSTidy and similar tools can check/fix the syntax but cannot sanitize the CSS for security purposes. I'm not sure such tools exist. New versions of the browsers introduce support for new CSS features pretty much every month. Don't think it is feasible even trying to sanitize all of them. The only way would be to severely limit what is supported then parse the CSS and remove everything else.