Google cache view is different from IE and FF

Discussion in 'Google' started by Blo, Jun 28, 2005.

  1. #1
    I realized that one of my pages looked different when viewed from the google cache, compared to normal rendering of the same page in both, IE and Firefox.

    I found out that I had small errors in my CSS file.
    How can I know that the Google cache will have problems BEFORE the page is indexed? What rendering technoloy is used?
    Blo.
     
    Blo, Jun 28, 2005 IP
  2. SEbasic

    SEbasic Peon

    Messages:
    6,317
    Likes Received:
    318
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Whatever the rendering technology of the browser viewing the page is.

    The reason it looks weird is because the page in in a frame, so your styles have been thrown out because of the top google frame.
     
    SEbasic, Jun 28, 2005 IP
  3. Blo

    Blo Guest

    Messages:
    39
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Are you sure that this is the only reason?
    Some of my fonts had the wrong size. It disappeared after I corrected the css file but it was never visible like that outside the google cache.
     
    Blo, Jun 28, 2005 IP
  4. SEbasic

    SEbasic Peon

    Messages:
    6,317
    Likes Received:
    318
    Best Answers:
    0
    Trophy Points:
    0
    #4
    My guess would be that your CSS had errors and the Google frame stuff accentuated them.

    Wait for the cache to update and I'm sure it will all be fixed. :)

    Absolute positioning is a killer for that stuff, just so you know. :)
     
    SEbasic, Jun 28, 2005 IP
  5. Blo

    Blo Guest

    Messages:
    39
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #5
    Exactly. But WHY? And what else can I do to find out despite waiting for the cache to show the latest modifications?

    Do you want me to save the source of the google cache and replace add the header box to my source in order to find out?

    I tried HTML validators but had no luck in this specific case.
     
    Blo, Jun 28, 2005 IP
  6. SEbasic

    SEbasic Peon

    Messages:
    6,317
    Likes Received:
    318
    Best Answers:
    0
    Trophy Points:
    0
    #6
    Again this is a guesstimate, but I would assume that as your CSS had errors, that there conflicts being caused with Google's own CSS for their sites.

    You can give it a go...

    Make sure you update all the locations to the CSS documents etc...

    Google don't like to validate it seems ;)
     
    SEbasic, Jun 28, 2005 IP
  7. mcdar

    mcdar Peon

    Messages:
    1,831
    Likes Received:
    110
    Best Answers:
    0
    Trophy Points:
    0
    #7
    This may not be the problem here but readers should note that if you use local paths for graphics and include files, once Google stores the cache of your page in a new location, the page will not have access to the original files.

    example:
    <!--#include file="includes/file.css"-->
    <!--#include file="http://www.mysite.com/includes/file.css"-->

    Caryl
     
    mcdar, Jun 28, 2005 IP