Announcement

Collapse
No announcement yet.

Fragment formatting difference in IE7, IE6 & FF

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Fragment formatting difference in IE7, IE6 & FF

    I have a wierd thing happening that I hope someone can explain.

    The following page shows a fragment called 'Plus Sizes?' at the end of the products:
    http://fancylines.co.uk/acatalog/Floral_Passion.html (Note: Lingerie Site)

    If I mouseover the fragment text in IE7 (beta) then all the text underlines. With IE6 or FF mouseover does not underline the text.

    I know IE7 is only beta but I'm curious if anyone else can also see this problem on my page and of course if anyone knows of a possible cause and solution.

    TIA

    Duncan R

    #2
    You are missing the closing </a> tag on the fragment anchor. Have a look at the source - it opens with an <a name= but the only closing </a> tag is after the hyperlink.

    For once IE is behaving correctly here and the other browsers have it wrong. Everything between the initial <a name and the </a is being treated as link text by IE7.
    Bill
    www.egyptianwonders.co.uk
    Text directoryWorldwide Actinic(TM) shops
    BC Ness Solutions Support services, custom software
    Registered Microsoft™ Partner (ISV)
    VoIP UK: 0131 208 0605
    Located: Alexandria, EGYPT

    Comment


      #3
      mmm - still confused - I see what you mean but I can't find where to close the anchor tag.

      Interestingly I also just noticed that the product names also show the same effect on mouseover in IE7 - you can see this for example on the same page (Even in FF).

      This is what I have in the fragment description:
      Code:
      !!<A large selection of items are available in <b>Plus Sizes</b>. 
      <br>To search for Plus items with <b>1X to 4X</b> sizes <a href="http://www.fancylines.co.uk/cgi-bin/ss000001.pl?SS=plus&PR=-1&TB=A&SHOP=" >CLICK HERE</a>.>!!
      Other fragments such as those on the homepage are ok.

      My fragments are all using the same slightly modified template (per Norman's column layout):
      Code:
      <script language=JavaScript>
      <!--
      if ( currentcol++ == 0 ) document.write('<tr><td colspan="3"><table border="0"><tr>');
      document.write('<td width="' + colwidth + '%" valign="top">');
      // -->
      </script>
      <noscript><tr><td width="100%"></noscript>
      NETQUOTEVAR:FRAGMENTANCHOR
      <table border="0" width="100%" cellspacing="5" cellpadding="1" bgcolor="#FFDFDF">
        <tr>
          <td width="100%">
          <h3>NETQUOTEVAR:BROCHURE_TITLE</h3>
          NETQUOTEVAR:BROCHURE_TEXT</td>
        </tr>
      </table>
      
      </td>
      <script language=JavaScript>
      <!--
      if ( currentcol >= CUSTOMVAR:FRAGCOLS )
      {
      document.write('</tr></table></td></tr>');
      currentcol = 0;
      }
      // -->
      </script>
      <noscript></tr></noscript>
      Any ideas how to close the anchor or what I've messed up?

      Comment


        #4
        Looking at this further I guess I can just put </a> after NETQUOTEVAR:FRAGMENTANCHOR in the template.

        I also looked at the base fragment template - there are no closing of anchor tags that I can see. Is this requirement to close anchors a newly enforced requirement that perhaps wasn't inlcuded in Actinic V7?

        Still don't understand why other fragments work ok (like the homepage) - perhaps it's to do with putting fragments on catalog pages vs brochure pages?

        Edit - Looked at the source of the fragments on the homepage and there are no anchors in the source. I have selected to exclude fragments from searches - maybe there's a buglet in V7 that removes the anchors in brochure pages but not product pages when the search is not selected for fragments.

        Comment


          #5
          You could try adding an explicit </a> after the NETQUOTEVAR:FRAGMENTANCHOR in each template.

          Interesting find - now I'm off to check my own fragments in IE7.
          Bill
          www.egyptianwonders.co.uk
          Text directoryWorldwide Actinic(TM) shops
          BC Ness Solutions Support services, custom software
          Registered Microsoft™ Partner (ISV)
          VoIP UK: 0131 208 0605
          Located: Alexandria, EGYPT

          Comment


            #6
            I tested the </a> and adding it in the template does provide a fix for the fragments.
            I'm stumped as to why the product names are underlining though - that seems to perhaps point to css - and happens in FF and IE7.

            Comment


              #7
              No, same thing - but different. Check out the position of the closing </a> tag in the product templates.
              Bill
              www.egyptianwonders.co.uk
              Text directoryWorldwide Actinic(TM) shops
              BC Ness Solutions Support services, custom software
              Registered Microsoft™ Partner (ISV)
              VoIP UK: 0131 208 0605
              Located: Alexandria, EGYPT

              Comment


                #8
                I can't see the missing close tag - on the same page for eg, the first product name looks ok to me:
                Code:
                <a name="a1_21DG3964"><span class="actregular"><b>Floral Sleepwear Babydoll</b></span></a>
                The tag is closed but underlines.

                I must be missing something...

                Edit - I can't see the missing close tag - there's a good phrase!

                Comment


                  #9
                  Sorry Duncan - moving the close tag to before the span will stop the underline - I was a bit cryptic, just saying check the position.
                  Bill
                  www.egyptianwonders.co.uk
                  Text directoryWorldwide Actinic(TM) shops
                  BC Ness Solutions Support services, custom software
                  Registered Microsoft™ Partner (ISV)
                  VoIP UK: 0131 208 0605
                  Located: Alexandria, EGYPT

                  Comment


                    #10
                    Now I see!!
                    I tested changing the position in the template and it solves the problem.

                    Thanks a lot Bill.

                    Looking back the positioning of the close tag is from the original Actinic Productline template.

                    Comment


                      #11
                      Originally posted by drounding
                      Looking back the positioning of the close tag is from the original Actinic Productline template.
                      Yes, it is. I think Norman was the first to spot that the position of that tag caused a problem in FireFox. Hopefully 'The Developers' have seen the conversations about this and will make the minor template change required for version 8.
                      Bill
                      www.egyptianwonders.co.uk
                      Text directoryWorldwide Actinic(TM) shops
                      BC Ness Solutions Support services, custom software
                      Registered Microsoft™ Partner (ISV)
                      VoIP UK: 0131 208 0605
                      Located: Alexandria, EGYPT

                      Comment


                        #12
                        Hopefully 'The Developers' have seen the conversations about this and will make the minor template change required for version 8.
                        Speaking as a 'Developer' (who tries to avoid MS products as much as possible) you will be pleased to hear that in the next Actinic version this problem will not be there.

                        Comment


                          #13
                          Thanks Chris. I expected you to be lurking
                          Bill
                          www.egyptianwonders.co.uk
                          Text directoryWorldwide Actinic(TM) shops
                          BC Ness Solutions Support services, custom software
                          Registered Microsoft™ Partner (ISV)
                          VoIP UK: 0131 208 0605
                          Located: Alexandria, EGYPT

                          Comment


                            #14
                            I overcame this by stripping out all the tables in the fragments (there are no tables on the page at all) and using a <div class="n"> and setting the CSS to ignore the <a> tags in the browser window


                            Bikster
                            SellerDeck Designs and Responsive Themes

                            Comment

                            Working...
                            X