Luminous Landscape Forum
The Art of Photography => The Coffee Corner => Topic started by: PeterAit on March 28, 2015, 08:40:47 am
-
Before I go bonkers, I am hoping someone can help me out. I am creating a new web page and the text formatting is controlled by a style sheet. It's pretty simple, with 2 CSS classes for headings and a style defining the appearance of <a> elements. In Dreamweaver's Design mode everything looks just as it should. But if I switch to DW's Live View mode only one of the heading styles is applied - the other heading style and the <a> style are ignored. This is also the case when I view the page in a browser. Why would only part of the style sheet be used and the rest ignored? Please save me from tearing my hair out!
-
Peter, Take a close look at your style sheet and make sure there's a closing curly brace for each opening curly brace. Also, make sure you're not trying to use an ID more than once. You can do that with classes, but not ID's.
-
You are my savior! It was a missing closing brace. It's still a mystery why the style sheet worked in design view, but as long as the problem is solved. THanks!
-
CSS Validation Service Check Cascading Style Sheets (CSS) and (X)HTML documents with style sheets (http://jigsaw.w3.org/css-validator/)
-
Isaac, if you're going to dump something like this into a discussion, how about explaining its connection to the discussion and what you think it means.
-
Isaac, if you're going to dump something like this into a discussion, how about explaining its connection to the discussion and what you think it means.
I think the phrase CSS Validation Service before the link to such a service tells you all you need to know. Pretty obvious I would have thought.
-
Peter solved his problem, Jeremy. The thread was finished. Peter wasn't trying to learn how to use DreamWeaver. He just overlooked something. Do you use DreamWeaver? Do you have even a remote clue about all this? As usual, Isaac was trying to stir things up. You know that as well as I do. Go ahead, Isaac. Click the Report to Moderator button.
-
As usual, Isaac was trying to stir things up. You know that as well as I do. Go ahead, Isaac. Click the Report to Moderator button.
What are those remarks or yours intended to do but "stir things up".
Perhaps Peter did not know that there are freely available services to error check CSS and HTML markup (http://validator.w3.org/). Now Peter will be able to use those services to save him from tearing his hair out in the future.
As usual, I was sharing knowledge.
-
You are my savior! It was a missing closing brace. It's still a mystery why the style sheet worked in design view, but as long as the problem is solved. THanks!
Hi Peter,
Glad you got things solved. It does remain odd that the style sheet seemed to work in design view though.
For a sanity check, a second opinion, I use tools like csslint.net (http://csslint.net), and similar for JavaScript (http://www.jslint.com/). One should not follow the suggestions blindly though, there are some coding preferences involved, as explained here (https://2002-2012.mattwilcox.net/archive/entry/id/1054/) and in a less confrontational manner here (http://code.tutsplus.com/articles/should-you-start-using-csslint--net-20895). However, it would have found the missing bracket though.
Cheers,
Bart
-
Peter solved his problem, Jeremy. The thread was finished. Peter wasn't trying to learn how to use DreamWeaver. He just overlooked something. Do you use DreamWeaver? Do you have even a remote clue about all this? As usual, Isaac was trying to stir things up. You know that as well as I do. Go ahead, Isaac. Click the Report to Moderator button.
Don't be such a numpty Russ. You are only showing how little you know by such a stupid post and being deliberately provocative to Isaac and now me.
I used to be employed to do web design as it happens and Dreamweaver was the tool of choice. Making such patronising assumptions only makes you look a fool.
Code validators/checkers as also suggested by Bart are a handy way of picking up simple errors that are easily overlooked by eye in amongst reams of code.
-
Okay, Jeremy. Yeah, code checkers are nice. And as you surely know, since you've been a heavy DreamWeaver user, DW has its own very useful code-checker.
-
Okay, Jeremy. Yeah, code checkers are nice. And as you surely know, since you've been a heavy DreamWeaver user, DW has its own very useful code-checker.
Using a different code checker is as Bart suggested a good second opinion.
-
If you actually think opinion matters in web development I can only conclude you haven't actually done it.
-
You can lead a horse to water, but you can't make it drink.
-
If you actually think opinion matters in web development I can only conclude you haven't actually done it.
That was a non-sequitur.
And your earlier response was an example of baiting. Who said the thread was finished? He simply provided another option for the OP to look up. It was no concern of yours.
Peter solved his problem, Jeremy. The thread was finished. Peter wasn't trying to learn how to use DreamWeaver. He just overlooked something. Do you use DreamWeaver? Do you have even a remote clue about all this? As usual, Isaac was trying to stir things up. You know that as well as I do. Go ahead, Isaac. Click the Report to Moderator button.
We're now waiting for you to say "Isaac, show us your pictures." That's the usual pattern.
This level of discourse belongs on dpreview.
-
Thanks for your penetrating insights, Robert. I'm sure you must be a DreamWeaver expert.
-
To the OP: I apologize for helping to derail your thread. I should have known better.
-
I should have known better.
Be prepared and listen, because they may say something and you may say, "Wait a minute . . . that doesn't make sense." So you do the follow-up question, sometimes a third follow-up question. Sometimes they keep saying no, bobbing and weaving, but the people watching know whether they're evading you or not (http://teacher.scholastic.com/scholasticnews/indepth/kids_primaries/tips/index.asp?article=russert). You don't have to lean over and choke them and say, "You're lying!" because if you do that, then the audience thinks that you're a bully and your guest is very sympathetic. But if you say three times, "I'm sorry, Senator, but I've asked you the question three times and you haven't answered," everybody goes, "Oh, they're ducking."
-
If you actually think opinion matters in web development I can only conclude you haven't actually done it.
Wrong again. Second opinion in this case does not literally mean opinion so do not be obtuse and pretend it does to score fake points.
-
To the OP: I apologize for helping to derail your thread. I should have known better.
You didn't derail anything Russ simply decided to be rude, nasty and personal when others were being helpful.
-
Code validators/checkers as also suggested by Bart are a handy way of picking up simple errors that are easily overlooked by eye in amongst reams of code.
And further on that note, I recently gave Microsoft Visual Studio a try and let it simply have a look at a style sheet (from the file explorer Open with Visual Studio, no need to create a project). I must say, it really gave useful suggestions when the WebEssentials extension is also installed. Sometimes suggestions as to 'Best Practice', sometimes useful (intelligent) additions for cross-browser compatibility, sometimes an error. Of course wen part of a project, VS can do much more like showing the direct impact on a webpage with a preview, but merely as a code checker it also works fine.
Cheers,
Bart