will the website look different once launched?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've been havingnightmares.
My first website is to be launched this week sometime.
I was wondering will my website look exactly like it does on the
pc where i've designed it?
I've test it in different revolutions.
Is there anything else i'm suppose to know?
Thanks in advance....
 
Chances are, no, it won't look exactly alike in all browsers. The best you
can hope for is that it will look as much alike as it needs to. The reason
is, not only do different screen resolutions make a difference, but also the
following:

1. Different browser window sizes can affect the layout of a page.
2. Different color resolutions can affect the colors in the page, although
this is slowly going away.
3. Different fonts are supported by different browsers. Only Times New Roman
is universally supported, although Arial is generally supported by all
browsers, although some support only Helvetica for a sans-serif font.
4. JavaScript can be supported or not in different browsers, and thus affect
the look of a page, if used for content manipulation.
5. ActiveX Controls in a page are not universally supported, and some
browsers that support it will disallow ActiveX.
6. Java Applets are not universally supported.
7. Flash presentations may or may not be allowed by the security settings.
8. Browser settings and defaults can affect layout that is not specifically
specified in the HTML.

Different browsers can render HTML slightly differently. In particular, CSS
can be problematic, although this is expected to go away in the next couple
of years. The Mozilla family of browsers, which includes FireFox, and the
most recent versions of Netscape, support the most current CSS standard as
defined by the W3C. However, Internet Explorer 6, the latest of the
Microsoft browsers, and one of the oldest of all browsers in use, does not
support the full standard. There are some significant differences in the
support for CSS in IE6, especially when it comes to margins and padding, and
how these are used in layout calculations. Internet Explorer 7, which will
ship with Windows Vista, is nearly out of beta testing, and is slated to
support (almost) the full standard specification. In the meantime, there may
be problems stemming from CSS, especially when used in conjunction with
JavaScript.

There are no doubt a few other minor considerations I've not thought of at
the moment, but I'll leave it to others to fill in any gaps.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist

I recycle.
I send everything back to the planet it came from.
 
Will my pictures be affected?
The other things I'm that worried about I'm pretty sure they might work
But other than that I'm like really stressed.
Should I devide all the stuff into folders and will my website host know
what to do?
I have no code in there just plain html code.
With a css. And that's all.
The flash i've got sorted out and I think the forms work now.
But maybe any other advice for a beginner?
 
FireFox is free, so you might want to download a copy for testing locally.
Unless there are color resolution differences on the machines, your pictures
will look the same (most systems now support 32-bit color, so it's not
likely to be a problem.

When you test in IE and FireFox, be sure to try and resize your browser
window to see how the page looks at different sizes.

And don't worry too much! You can always fix anything that isn't exactly
right. At least you're asking the right questions, and concerned about the
right things. :)

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist

I recycle.
I send everything back to the planet it came from.
 
Why be stressed? Almost everything can be fixed...or redone :-)
And...why wait? Get it up there...the sooner the better...then you can get
some real help if something is wacked.

You should organise your files in whatever manner makes organizational sense
to you. Usually, the mess is caused by where to keep images. Some people
keep them in the root (a mess if you ask me) some people keep them in the
images folder and subfolders (I do) others keep them in folders based upon
pages (lately this is making more sense to me).

Will your host know what to do?...dunno. Based upon postings in here a lot
of hosts don't know anything...so make sure you have a good host...but
there's not much they really "do" anyway.

Will your pictures be affected? ... dunno what you mean. They shouldn't
change unless you've done something weird. Make sure you have resized and
optimized them outside of FP then Import them for use into FP (this is a
common mistake made by newbies...and some oldbies too)

hth


| Will my pictures be affected?
| The other things I'm that worried about I'm pretty sure they might work
| But other than that I'm like really stressed.
| Should I devide all the stuff into folders and will my website host know
| what to do?
| I have no code in there just plain html code.
| With a css. And that's all.
| The flash i've got sorted out and I think the forms work now.
| But maybe any other advice for a beginner?
|
| "Kevin Spencer" wrote:
|
| > Chances are, no, it won't look exactly alike in all browsers. The best
you
| > can hope for is that it will look as much alike as it needs to. The
reason
| > is, not only do different screen resolutions make a difference, but also
the
| > following:
| >
| > 1. Different browser window sizes can affect the layout of a page.
| > 2. Different color resolutions can affect the colors in the page,
although
| > this is slowly going away.
| > 3. Different fonts are supported by different browsers. Only Times New
Roman
| > is universally supported, although Arial is generally supported by all
| > browsers, although some support only Helvetica for a sans-serif font.
| > 4. JavaScript can be supported or not in different browsers, and thus
affect
| > the look of a page, if used for content manipulation.
| > 5. ActiveX Controls in a page are not universally supported, and some
| > browsers that support it will disallow ActiveX.
| > 6. Java Applets are not universally supported.
| > 7. Flash presentations may or may not be allowed by the security
settings.
| > 8. Browser settings and defaults can affect layout that is not
specifically
| > specified in the HTML.
| >
| > Different browsers can render HTML slightly differently. In particular,
CSS
| > can be problematic, although this is expected to go away in the next
couple
| > of years. The Mozilla family of browsers, which includes FireFox, and
the
| > most recent versions of Netscape, support the most current CSS standard
as
| > defined by the W3C. However, Internet Explorer 6, the latest of the
| > Microsoft browsers, and one of the oldest of all browsers in use, does
not
| > support the full standard. There are some significant differences in the
| > support for CSS in IE6, especially when it comes to margins and padding,
and
| > how these are used in layout calculations. Internet Explorer 7, which
will
| > ship with Windows Vista, is nearly out of beta testing, and is slated to
| > support (almost) the full standard specification. In the meantime, there
may
| > be problems stemming from CSS, especially when used in conjunction with
| > JavaScript.
| >
| > There are no doubt a few other minor considerations I've not thought of
at
| > the moment, but I'll leave it to others to fill in any gaps.
| >
| > --
| > HTH,
| >
| > Kevin Spencer
| > Microsoft MVP
| > Professional Chicken Salad Alchemist
| >
| > I recycle.
| > I send everything back to the planet it came from.
| >
| > | > > I've been havingnightmares.
| > > My first website is to be launched this week sometime.
| > > I was wondering will my website look exactly like it does on the
| > > pc where i've designed it?
| > > I've test it in different revolutions.
| > > Is there anything else i'm suppose to know?
| > > Thanks in advance....
| >
| >
| >
 
What does the DOCTYPE do?
I need to have a doc type according to the http://validator.w3.org that was
given to me, which I thank so much for!
That will probably let me sleep way better.
But what should I exactly do in the DOCTYPE.
I'm so sorry for all the hassle people, as you can see I'm way beyond par
for creating a website. But i'm trying. And the company's paying me to.
All the help is really appreciated. Thank You all you wonderful people.

Daniela
 
The doctype does two things -

1. It tells the validator what kind of document scheme to use to validate
the page, and
2. It tells the browser how to render the page (there are only two
choices - 'quirks' mode, and 'standards' mode)

The first purpose is what doctypes were designed to do. The second purpose
is what browser manufacturers realized they could use them for, and have
done so ever since - this is called 'doctype switching'.

Quirks mode is how browsers USED to work all the time - each browser had its
own special quirks and would render the page as *IT* thought it should.
Quirks mode is quite tolerant of invalid HTML and in IE, quirks mode makes a
valiant effort to render what it thinks you intended, rather than what you
actually wrote.

Standards mode, however, means that a) the browser expects to see valid
HTML, and b) it renders that HTML according to the standards published by
the W3C. Usually. Sorta. Most of the time.

Relying on Quirks mode to achieve the layout you desire is the cause for
50% of the posts here about "why doesn't my page look the same in ...".
Click to expand...
It's generally just a bad idea. Who knew? 8)

How do you select the proper doctype? You select it based on your ability
to enforce proper usages. YOU have to do this. Placing any particular
doctype on your page will not prevent FP from making non-standard code *if
you tell it to*, like, for example, applying a background image to a <tr>,
or adding a height attribute to a <table> tag. The trick is to choose a
doctype commensurate with your ability (HTML4.01 Transitional is a good one
to start with) and with your needs (if you are working with XML/XSLT, you
must use an XHTML doctype), and then validate often to catch the errors.

Another (unspoken) trick is to UNDERSTAND THE WARNINGS generated by the
validators, but we can go there later!

Anyhow - an HTML 4.01 Transiltional doctype looks like this -

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

(I am showing the <html> tag, to show you that it should be the first thing
on the page)
 
Thank You so much Murray,
I have two problems that keeps on being detected by the
http://validator.w3.org
"there is no attribute background" & "there is no attribute color".
Will it matter if I don't change it?
Or should I find a way of changing it?

Daniela
 
"there is no attribute background"
"there is no attribute color".
Click to expand...

This means that you are using a background (or color) attribute, and the
doctype you have selected doesn't allow that. Most of those
'presentational' attributes have been deprecated in favor of CSS - that's
why you are getting the error. Remove that attribute from the tag, and
simply create a CSS rule that does the same thing.
 
Daniela said:
I've been havingnightmares.
My first website is to be launched this week sometime.
I was wondering will my website look exactly like it does on the
pc where i've designed it?
I've test it in different revolutions.
Click to expand...

Well, if there's a REAL revolution, a lot of things might look different...
:-D
 
Thank You P@tty that was my mistake.
Anyhow every page is now gives me this message,
but I don't know what it means.
Can anyone please explain it to me?
"The uploaded document was checked and found to be tentatively valid HTML
4.01 Transitional. This means that with the use of some fallback or override
mechanism, we successfully performed a formal validation using an SGML or XML
Parser. In other words, the document would validate as HTML 4.01 Transitional
if you changed the markup to match the changes we have performed
automatically, but it will not be valid until you make these changes. "

Thank You
 
Daniela said:
Thank You P@tty that was my mistake.
Anyhow every page is now gives me this message,
but I don't know what it means.
Can anyone please explain it to me?
"The uploaded document was checked and found to be tentatively valid HTML
4.01 Transitional. This means that with the use of some fallback or
override
mechanism, we successfully performed a formal validation using an SGML or
XML
Parser. In other words, the document would validate as HTML 4.01
Transitional
if you changed the markup to match the changes we have performed
automatically, but it will not be valid until you make these changes. "
Click to expand...

I've never seen that message before, but it sounds like it's suggesting
certain changes to you, which, if you make them, will allow the page to
validate.

Keep in mind, Daniela, that validation is sort of like spell-checking. It's
an automated test to see if your code is basically sound, and to point out
parts of the code that you *might* want to change to match the official W3C
specifications. It's not a hurdle you have to get over in order to have a
decent web page, but a set of guidelines.
 
Back
Top