Internet Explorer versions 7 and 8.

Discussion in 'Internet Explorer' started by egosterberg, Jun 21, 2009.

  1. egosterberg

    egosterberg Guest

    IE 7 and 8 on Windows XP is not displaying the Web site menu of the web pages
    produced by Publisher 2007. The index.htm and index_files are uploaded to
    the Web site. It only displays the first page on the Web Site.

    Firefox 3.0.10 on Windows XP displays the Web site menu correctly and
    permits the selection of the menu options.

    Firefox 3.0.11 and Internet Explorer version 4 on an iMac both display the
    Web site menu correctly and permit the selection of the menu options.

    Please fix Internet Explorer so that it runs correctly on Windows XP



    --
    E.G. Osterberg

    ----------------
    This post is a suggestion for Microsoft, and Microsoft responds to the
    suggestions with the most votes. To vote for this suggestion, click the "I
    Agree" button in the message pane. If you do not see the button, follow this
    link to open the suggestion in the Microsoft Web-based Newsreader and then
    click "I Agree" in the message pane.

    http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
     
    egosterberg, Jun 21, 2009
    #1
    1. Advertisements

  2. egosterberg

    Gordon Guest

    Err WHY are you using PUBLISHER to construct a website?
     
    Gordon, Jun 21, 2009
    #2
    1. Advertisements

  3. egosterberg

    Gordon Guest

    In addition:
    My web pages constructed using Kompozer( get it here: it's free!
    http://kompozer.net/)show perfectly in both IE8, IE7 and Firefox.
     
    Gordon, Jun 21, 2009
    #3
  4. egosterberg

    C A Upsdell Guest

    The problem is likely that Publisher 2007 is producing broken code.
    Others have complained the same, at least in regards to Publisher and
    IE8. If a standards-compliant browser sees broken code, badly rendered
    pages are likely. Use a better tool than Publisher 2007.
     
    C A Upsdell, Jun 21, 2009
    #4
  5. egosterberg

    egosterberg Guest

    Microsoft Publisher 2007 is used by many academic institutions and it saves a
    lot of time because it has templates that a non-technical individual can use
    to create community web sites.

    It is expected that the Microsoft IE browser should be able to process
    Microsoft Web publisher web site pages and in fact previous versions of IE
    did not have this problem.
     
    egosterberg, Jun 21, 2009
    #5
  6. egosterberg

    egosterberg Guest

    Please read my first posting which states that previous versions of IE and
    Firefox on both the iMac (Macintosh) OS and the PC Windows XP OS process the
    Publisher web pages correctly.

    Because Firefox and previous version of IE can process the Publisher pages
    correctly on a Mac and a PC, does this not indicate there is a problem with
    the newer version of IE 7/8?
     
    egosterberg, Jun 21, 2009
    #6
  7. egosterberg

    Gordon Guest


    I don't think so!
    Which is why there are so many badly coded websites around.
    Many PROPER web site applications also have templates - you can also
    find many templates free on the internet

    Why? How long have you been using MS applications?

    and in fact previous versions of IE

    Previous versions of IE were far more forgiving to bad code.....

    I repeat - use a PROPER web page designing app. Publisher was NOT
    designed to code web pages...
     
    Gordon, Jun 21, 2009
    #7
  8. egosterberg

    egosterberg Guest

    You sound like IBM.

    I am not the user of web page design. I have been a developer since the
    1960s on all types of computers and networks, developing operating system,
    network, scientific and commercial applications.

    You should be more open minded to all kinds of software and telling someone
    to use other software because you guess that there is a problem with the
    another product.

    The standard is to provide backward compatability with products unless a
    notification to all users is given that a feature is no longer going to be
    supported.
     
    egosterberg, Jun 21, 2009
    #8
  9. egosterberg

    Gordon Guest

    Yes and if you use a PROPER web design application that produces web
    pages coded to w3 standards then EVERY browser will render the pages
    correctly.
    I repeat - PUBLISHER IS NOT A WEB SITE APPLICATION.
     
    Gordon, Jun 21, 2009
    #9
  10. PA Bear [MS MVP], Jun 21, 2009
    #10
  11. egosterberg

    Ron Sommer Guest

    Are you defending Publisher because it does a good job of writing code?
    Word will also write HTML code, but the code that is produced has several
    pages of extra language that is never used. I would not recommend using
    Word for html code.
    Do you have examples?
     
    Ron Sommer, Jun 21, 2009
    #11
  12. Gazing into my crystal ball I observed =?Utf-8?B?ZWdvc3RlcmJlcmc=?=
    Then it should not be a shock to you that the bad code Publisher
    generates is breaking your website(s). An important part of development
    is testing, you know that. Had you tested your website against standards
    you would have seen scores of errors.
    The issue here is that the tool chosen produces bad markup for the
    application for which it is being used.

    You can use olive oil instead of butter when making chocolate chip
    cookies, and they will be edible, but they won't taste good, and they
    won't bake up correctly.

    Microsoft _does_ make programs that are intended for making web sites. I
    can't say anything much about them because I code everything by hand, but
    they do exist.

    Why should Microsoft, of any software developer for that matter, take
    into consideration making allowances for a program that is not being used
    for its intended purpose.
    You need to read the specs. This has NOTHING to do with being backwards
    compatable. The markup Publisher produces is just garbage. IE8 is fine
    with markup that is written to standards.

    I don't know if you have heard of the Acid3 test. So far, there is only
    one browser that passes - Safari 4 comes in at 100%, the next browser is
    Opera 10 at 99%, Firefox fails miserably, and reports are that IE8
    crashes (I don't know - my IE8 is hanging today for some reason).

    Why is the Acid3 Test important? It is a gauge to see how well a browser
    is evolving. New standards and technology are coming, and browsers must
    be able to support the current technology in order to go on. Sometimes
    that involves not supporting incompatible code.
     
    Adrienne Boswell, Jun 21, 2009
    #12
  13. egosterberg

    C A Upsdell Guest

    No, IE7 and IE8 comply with the standards better, hence are less
    tolerant of broken code. Firefox may have rendered the pages as you
    expect, but this can happen simply because it happens to do something
    which you consider reasonable when it encounters the broken code. The
    standards say what browsers should do with proper code, but they do not
    say what browsers should do with broken code, so different browsers may
    deal with broken code differently.

    Try validating the pages: I suspect that you will be surprised.
     
    C A Upsdell, Jun 21, 2009
    #13
  14. egosterberg

    C A Upsdell Guest

    Well, I have been a developer since 1971, so my experience is almost as
    ancient as yours.

    The issue is not so much that features have changed with IE7 and IE8:
    the issue is that long-standing bugs in IE have been corrected.
    Standards were produced about 10 years ago for how browsers should deal
    with valid HTML and CSS code in web pages, and Microsoft was a key
    player in defining these standards: but unfortunately it has only been
    recently that browsers have complied with the standards very well, and
    IE has, alas, been a little behind its competitors. You should blame
    the software which has created defective code, not the browsers which
    have been fixed and which therefore process the defective code differently.

    You are not the first person using Publisher 97 who has made a similar
    complaint. What you should be doing, instead of blaming IE7 or IE8, is
    either (a) blaming your choice of Publisher, or (b) blaming Microsoft
    for selling a tool which creates defective code. You need a better
    tool: if you want to continue to use Publisher, you should see if
    Microsoft has an update for it which creates better code.
     
    C A Upsdell, Jun 21, 2009
    #14
  15. See the following KB article for the cause of this issue and the workaround:
    http://support.microsoft.com/kb/969705

    Good luck,

    Donald Anadell
     
    Donald Anadell, Jun 22, 2009
    #15
  16. Nice catch!

    From the Workarounds section:

    <QP>
    Republish the Web site by [sic] using Publisher 2007 Service Pack 2.

    Note: Publisher 2007 Service Pack 2 is scheduled to release on April 28,
    2009.

    For Publisher 2003 users, please upgrade to Publisher 2007, and then install
    Publisher 2007 Service Pack 2.
    </QP>
     
    PA Bear [MS MVP], Jun 22, 2009
    #16
  17. egosterberg

    VAmp Guest

    Thanks for the hint- That realy helped me out- I used to run a small business
    and I would help other small business's who were sold the Office Suite as a
    be all for small business - I think it is pretty poor of Microsoft to create
    a product - sell it as something to create web- pages (ignoring the holy war
    on if the pages created are good or not) and then turn around and make the
    whole thing incompatible - with thier own product- now all those people have
    to upgrade to 2007 and then spend the time and or money to redesign their
    sites - more money for Microsoft - less money for small businesses who get
    stuck with the bill ones again.


     
    VAmp, Jul 28, 2009
    #17
  18. [YW. Office 2003 SP3 (including Publisher 2003) and WinXP SP3 are both on
    Extended Support. This means that there will be no new/additional features
    added and only critical security updates will be offered. No updates of any
    kind will be offered after April 2014.]
     
    PA Bear [MS MVP], Jul 28, 2009
    #18
  19. egosterberg

    egosterberg Guest

    --
    E.G. Osterberg


     
    egosterberg, Jul 28, 2009
    #19
  20. egosterberg

    egosterberg Guest

    --
    E.G. Osterberg


    Guess what, IE 8 was truncating the html pointer and Microsoft fixed it so
    it can now display the Publisher Menu/Pages correctly as it should.
     
    egosterberg, Jul 28, 2009
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.