Hi all,

 

Just wondering if anyone has come across this issue before. I work in Dreamweaver and have never seen this before. I was adding some Media Queries and couldn't figure out why some were not working. After searching online I found a post of someone saying that there was some odd code added to their CSS.

 

I looked in the page source and sure enough there was some odd code. The answer provided by the original poster was to copy the code into Word and copy it back to Dreamweaver. I had done this and it worked - the odd code was gone.

 

Attached is a screenshot of page source with the odd code highlighted.

Edited November 20, 201411 yr by mrludable

I don't use Dreamweaver personally but those wierd bits of code look like special characters that DW is adding to the CSS when it generates it.

 

Perhaps there is a setting in DW that you can change?

one more reason not to use dreamweaver

Oi oi I use Dreamweaver, be it macromedia still and 2002

Oi oi I use Dreamweaver, be it macromedia still and 2002

In general I see nothing wrong with it to be honest except when you get people using the wysiwyg and not checking their code ugh!!

In general I see nothing wrong with it to be honest except when you get people using the wysiwyg and not checking their code ugh!!

 

 

If you already have it, and only use code view. Then sure go for it. But there is absolutely no reason to go out of your way to use it. There are much better and cheaper/freeier options. Plus here in America you wouldn't get a job as a web developer at a serious shop if you mention you use Dreamweaver as your coder because it comes with a perception that you don't know what the crap you are doing.

Never used the WYSIWYG editor, always code myself, which is why I don't understand how it got there...

In general I see nothing wrong with it to be honest except when you get people using the wysiwyg and not checking their code ugh!!

 

Agreed. I still use it for the sync and file manager really, probably better out there but it forces me to code as it has no idea what a media query is

I wonder if that's a carriage return ...

You see, when typewriters existed, "new line" and "carriage return" were two commands. When hitting the "enter" key, some operating systems sent both commands to properly emulate the experience. This is why the symbol on the "Return" key is ...

 

... oh, yeah, solutions ...

 

Dude, this is Prepros. It compiles files such as LESS, SASS, JavaScript, Coffeescript ... more useful is the fact that it can compress CSS files and watch your folder (so saving in Dreamweaver will automatically compress your file). The minified file wouldn't have that weird character in it (would load faster too because it's a smaller file). To top it all off, Prepros is free. Might be worth a shot.

I wonder if that's a carriage return ...

You see, when typewriters existed, "new line" and "carriage return" were two commands. When hitting the "enter" key, some operating systems sent both commands to properly emulate the experience. This is why the symbol on the "Return" key is ...

 

A good test would be to leave no line space between the media queries. The other theory is Dreamweaver does not quite understand the nested css structure; media queries is the only thing I can think of in css where you have double braces, normally you have a pair { } with a semicolon to close each part, so it likes anything like { color: blue; } and maybe { { } } has a bug and wasn't spotted in bug testing.

 

I know since I use a really out of date version of Dreamweaver most of my css is underlined red

Edited November 22, 201411 yr by BrowserBugs

If you use a combination of sublime with a task runner such as grunt it negates any of the benefits of automation that DW accomplishes and grunt is almost infinitley customisable. Sublime also has a boat-load of keyboard shortcuts and a large array of plugins for things such as Emmet to really speed up the coding process.

 

I see no reason to use DW especially when it cannot even handle media querys.

 

 

Yes using something like grunt has a learning curve but that's the nature of this industry you have to learn and adapt or you get left behind. Command line task runners like grunt and version control etc are here to stay, and I see more things heading down this path in the future. We should all be learning the command line and getting used to using programmable tools (grunt uses js). My rate of production would plummet if I didn't have grunt, git or ssh server access.

Edited November 24, 201411 yr by rbrtsmith

That might be it BrowserBugs, I use CS5 so it's a little old...

That's why I gave up using DW and switch to Sublime Text instead.

Will have to give Sublime a go...

If you use a combination of sublime with a task runner such as grunt it negates any of the benefits of automation that DW accomplishes and grunt is almost infinitley customisable. Sublime also has a boat-load of keyboard shortcuts and a large array of plugins for things such as Emmet to really speed up the coding process.

 

I see no reason to use DW especially when it cannot even handle media querys.

 

 

Yes using something like grunt has a learning curve but that's the nature of this industry you have to learn and adapt or you get left behind. Command line task runners like grunt and version control etc are here to stay, and I see more things heading down this path in the future. We should all be learning the command line and getting used to using programmable tools (grunt uses js). My rate of production would plummet if I didn't have grunt, git or ssh server access.

 

This x1000. I love Grunt and wouldn't dream of doing a site without it.

 

This x1000. I love Grunt and wouldn't dream of doing a site without it.

 

It would be a nightmare, I think I have over 10 grunt tasks running on most projects, if you can think of something that can be automated somebody probably already has written a grunt task for it Plus it's also useful for code feedback like the jsHint task and so forth.

Edited November 24, 201411 yr by rbrtsmith