You shoukd not really use wysiwyg editors to do code and you shoukd aso avoid doing inline CSS like that.
That's not really CSS.
The edit will not deal with incorect HTML and CSS very well, it will try fix it up if it's not correct.
Good CSS is external stylesheets where one change will effect all instances throughout a site.
There are also plenty of free and paid coding apps out there for mac and PC that have all the tools and features to help with the coding, code highlitng and more.
Yes, I am perfectly aware of style sheets etc. Nevertheless, when I am working on a "look," and need to just tweak something, I do consider it a bug when it erases ALL the html if the css is not what it is looking for. It used to be that it would just delete the offending css statement.
At the very least, it could highlight the offending line, point out the percieved error and give someone a chance to fix it first?
Won't be the CSS, it will be that it was not closed off or style was spelt wrong or a > knocked off and on save th editor tried to fix it up.
Katie, won't be a bug, just that inline editors are not the place to do coding in, if there is an error they will just apply logic to try make them valid.
Pretty much when you get into web development you read and see, just as people say when writing online content as well that you never do it in these editors.
Because you can jump off a cliff and there may be even a sign saying "Jump here" Does not mean you do hey
Yep the editor is not the best out there but I defiantly have seen many online editors mess up things, especailly trying to code in them.
Considering there is some free coding apps as well as paid out there I personally do not understand why you would try to code in these anyway.
Coming from a novice, I find that writing the simple doctype at the top ala HTML 5, and having Dreamweaver do its W3 validation thing usually points out my errors. More and more, I find what you are saying to be completely true, Liam. Pure coding may be the closest thing to being on the road toward good results . . . . HOWEVER, IE still messes me up sometimes. For example, of all the browsers, it was the only one recently to render my footer under the content portion of a page. not under the way I wanted it to, under ala z levels. It was weird. Couldn't figure it out, and still haven't. Magically, however, the next day it didn't anymore. It is the unexplained and mysterious that I still struggle with , be it HTML, CSS, whatever . . .
IE is crap, pure and simple so you need to be aware of it.
Missing a ; and chrome and firefox will be fine but IE halts on all errors, which in some ways is good for that. But HTML badly formed it falls over.
Doing web standards, coding good CSS, knowing really well what your doing, just like in any job from plumber to electrician then all you then have to think about it what are the IE bugs.
My IE only stylesheets are quite small these days because of these principles.
It is not about being "I am better then you" But if you follow web standards, good code, best pracatace etc you just have less problems and the perfomance of sites you build increase.
Using code editors that not only quick populate your code, easy to follow and look at and provide the tools you need means you get the job done correctly and effeciently.
It is like having the job to saw wood. You got a guy trying to do it on his lap, or the guy using the bench and clamp. Just because you can do it both ways, which gets the better cut and is less hassle and also safer?