check the basic syntax of the custom CSS when saving

[ratcreature]

Title:
check the basic syntax of the custom CSS when saving

Area:
styles

Summary:
It would be neat if on the Customize Journal Style page the field for "use embedded CSS" would check whether the CSS syntax is valid, i.e. whether all brackets and semicolons etc are there, and alert you if the CSS was invalid before saving.

Description:
When I put in "Custom CSS" (mostly just to change small things like having the icon on the left rather than the right and such) I test the CSS first in only my browser (usually with the FF Stylish extension) and check it there and then c&p it in the field. Sometimes without noticing my c&p misses a starting . or a closing } or such, I save and then am confused that it doesn't work.

It would be useful if the input form could alert me if the CSS was invalid right away. It would be even more awesome if the CSS field had a preview option showing how the custom CSS I entered will change my journal, because then I wouldn't need to use the Stylish extension to try out the CSS at all.

Poll #1012 check the basic syntax of the custom CSS when saving

Open to: Registered Users, detailed results viewable to: All, participants: 32

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
17 (53.1%)

Should be implemented with changes.
7 (21.9%)

Shouldn't be implemented.
2 (6.2%)

(I have no opinion)
6 (18.8%)

(Other: please comment)
0 (0.0%)

Comments

[zarhooie]

I said I have no opinion, but that's a lie. I think that while aiming to check the custom CSS of users is an admirable goal, I'm a little concerned that people may blame DW if the cleaner doesn't catch their mistake. I am more comfortable keeping the system as-is.

[ratcreature]

I think most people know that autochecks aren't perfect though. Anyone who has used validators knows that, even everyone who ever only used a spellcheck knows that autochecks don't guarantee a perfect result. They just help reduce some errors. I think the concept is familiar enough that the expectations won't be unreasonable.

[zvi]

I'm more interested in the preview than the validator, honestly. But either/both is good.

[archangelbeth]

Same here; a previewer would make me actually interested in learning a few CSS tweaks.

[triadruid]

This. Preview is a lot more useful for those of us who CAN manage our css, at least most of the time... having to keep another tab open and remembering to reload the whole thing each time I make a change is a colossal pain.

[turlough]

I have the same concern re the cleaner as zarhooie but I'm all for a preview option for the custom css.

[susanreads]

Me too.

[msilverstar]

I'd like both a validator (inform me of significant errors) and a preview (let me fiddle until I get it right)

[7rin]

Yes. I might not mess with CSS very often, but it'd be useful to be able to see what I'm doing before I commit it.

[birguslatro]

I go with a validator and previewer too.