• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 212
  • Last Modified:

New web pages displary right in Internet Explorer and wrong in Firefox

I am updating one of my web sites.
In Firefox two test pages show all wrong, but they show up fine in Internet Explorer.

Help would be apprecaited

Test page one:  http://www.thebicycleiste.com/testing/index-2007b.html

Test page two: http://www.thebicyclesite.com/testing/yahoosports.html
0
glenn_1984
Asked:
glenn_1984
  • 4
  • 2
  • 2
  • +1
1 Solution
 
Ajay SharmaCommented:
first page is not accessible

Second page is not looking ok in firefox and IE

Second Page:
In IE scroll to right the vertical scroll comes after that
0
 
glenn_1984Author Commented:
First link fixed:  http://www.thebicyclesite.com/testing/index.html

I am not sure what you are saying here:
"Second Page:
In IE scroll to right the vertical scroll comes after that
back to top "
0
 
ravi_raj123Commented:
Try this option:

<META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"> This directive indicates cached information should not be used and instead requests should be forwarded to the origin server. This directive has the same semantics as the CACHE-CONTROL:NO-CACHE directive and is provided for backwards compatibility with HTTP/1.0.
Clients SHOULD include both PRAGMA:NO-CACHE and CACHE-CONTROL:NO-CACHE when a no-cache request is sent to a server not known to be HTTP/1.1 compliant.
HTTP/1.1 clients SHOULD NOT send the PRAGMA request-header. HTTP/1.1 caches SHOULD treat "PRAGMA:NO-CACHE" as if the client had sent "CACHE-CONTROL:NO-CACHE".

And also check this link for Configuration of cache on Apache,
http://www.pantz.org/webservers/apache/httpdexample.shtml

Good Luck,
Ravi
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
ravi_raj123Commented:
I am sorry, I have post my comments to the wrong question. Ravi
0
 
av8r1s2flyCommented:
Hi Glenn,

The problem with both pages seems to be non-conformance to the doctype definition:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">

I removed it and the page appears fine on both browsers. Perhaps you need to use the correct definition or change your HTML to conform to the one you have used.

Check out this link for a comparison of the doc types: http://en.wikipedia.org/wiki/Quirks_mode#Comparison_of_document_types
0
 
glenn_1984Author Commented:
That worked.

What is the net impact of No Document Type, however?
0
 
av8r1s2flyCommented:
Not declaring the doc type invokes what they call the "Quirks" mode of the browser. The other modes are "Standards" mode and "Almost Standards" mode. (For details refer to http://en.wikipedia.org/wiki/Quirks_mode)

It seems there are certain CSS features that work only in the standards mode of the browsers. Since your pages are working properly in quirks mode, it would be safe to assume you are not using any such features. But in the future, you need to take care that whatever changes are done, they continue to work in the same mode.

But, needless to stay, it's always best to comply with stand our pageards. Try and rectify your pages to be strictly XHTML compliant (assuming that's what you were trying in the first place). Till then, you can continue to display without the doctype declaration.

All the best!
0
 
av8r1s2flyCommented:
A slight correction.. it's not just CSS features but also flexibility of HTML syntax that differs with browser mode.
0
 
av8r1s2flyCommented:
.. and some typo: "it's always best to comply with stand our pageards" = "it's always best to comply with standards"
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now