I have a new master site sitting in beta right now. Probably the result of about a months hard work.
The whole enchilada. My entire portfolio and full second round marketing strategy that I want to go off at once.
There is a firefox issue with an <h1>
tag. It is putting a line break after it and moving everything down to the next line.
Does anyone know why this would happen? It is clean in some other browsers such as Safari and Opera.
I am not ready to launch it. But I have a margin issue that I cannot fix.
I have the
<meta name="googlebot" content="noindex"> <meta name="googlebot" content="nofollow"> <meta name="googlebot" content="noarchive">
In the head.
And I just want to follow best practices. If I post a link. Will it start showing up other places half finished? Is there a way I can just make it like it does not exist but I can give people links but it will never pick up any visibility?
Most importantly. Can anyone tell me where the line break is coming from?
Er. H1 is a block element and
Er. H1 is a block element and there is, by default, a line break after it. If you don't want one you have to change that behavior in your CSS.
Can you tell me how?
Can you tell me how to do that?
Well, if you don't already
Well, if you don't already understand CSS and html enough to do even that I hesitate and wonder where to start and what to explain.
I think you should probably start by going to "htmldog.com" and start working through the tutorials. You don't seem to understand things well enough to create a real site. Are you using one of the dreaded and ugly and horrible "WYSIWYG" web page editors like Dreamweaver by chance? If so it's time to stop and lean real html and CSS.
Or perhaps you could do as the posting guidelines suggest and post either ALL your code or give us a link to the site.
Also, I would recommend
Also, I would recommend using
<meta name="robots" content="noindex,nofollow">
Thanks
I appreciate the help.
I am sure it is somewhat of a novice question.
I have not had formal training. Though I can do a great deal.
There are advanced questions I know I can answer. And a novice few I know I can't.
I learned it on my own. And I know pride can be the biggest obstacle.
I just want to know how to prevent that line break. I don't like the display inline options and such.
Any help is appreciated.
Quote: I have not had formal
I have not had formal training.
there isn't such a thing, non of us have had formal training, web development is a multi disciplined catchall we have all had to learn the hard way - the only way. If you want formal training you could become a MCSE or better a Cisco certified engineer
Why is this 'line break' an
Why is this 'line break' an issue? have you attempted to control things via the elements margins?, floating an element will cause the following elements to sit alongside it - in theory! but depends on certain factors.
Is this site online? if so please post a link if necessary separate the url if you are concerned:
example dot com
t-bone_two wrote: I have not
I have not had formal training.
Well, neither have I, and I'll bet neither have any of the really good coders who post here. It's hard to get formal training in html that is worth anything.
There are advanced questions I know I can answer. And a novice few I know I can't.
I learned it on my own.
It's more important with html to understand the basic concepts, and you appear not to. That's why I suggested you go to the Html Dog site and work through the tutorials there, starting with the html tutorials.
I just want to know how to prevent that line break. I don't like the display inline options and such.
Any help is appreciated.
You ask for help, but you've already ruled out the proper solutions! To prevent a block element from ending with a new line you have two, and only two, options. Either set it to "inline" with CSS or you float it. If you don't like either then you should learn to like them, because that's all ya got.
Thanks!
You answered my question.
Very informative and helpful.
I didn't know if display:inline was considered a bad practice. So you gave me what I needed.
Thank you Ed. I appreciate your straight shooting.
t-bone_two wrote: I didn't
I didn't know if display:inline was considered a bad practice.
The purpose of CSS is to control the presentation of html elements, so if you want an element to display differently from the defaults, using CSS to do it is always good practice.
Ideally, presentational considerations should be entirely kept out of your html. HTML is designed to mark up the meaning of content. When deciding what tag to use your only consideration should be which tag best represents the meaning of the content it is enclosing.
The whole idea of CSS in the first place is to allow you to separate content from it's presentation. HTML is meant to be used to mark up the content according to it's meaning, or syntactical structure. This is known as "semantic html" and it is a vital concept you should look up on the internet. This is the good old programming concept of "separation of concerns" transferred to the web.
Of course the ideal is not reachable in actual practice, but you can come very close, and if you learn to do that and make it a habit as far as possible to always write valid and semantic html in a STRICT document type you will find that, once you have learned how to do it, CSS becomes actually quite easy and you will make far less errors, and save yourself bags and bags of time and trouble.
how to do
i want known how to do that??
spam link deleted --gt