FF -> Safari/Opera Float inconsistency

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Wouter

    FF -> Safari/Opera Float inconsistency

    Hey hi....

    I get this weird inconsistency in Firefox using floats.

    I made this little demo of it wich u can find here:


    Now the ? Question mark should be in the grey bar, as it is in Safari and
    Opera however in FF it's floating beneath it.

    Anybody know of a workaround / fix?

    Tia
    Immo

  • dorayme

    #2
    Re: FF -> Safari/Opera Float inconsistency

    In article <C2E88B94.1076F %stop@spam.nl>, Wouter <stop@spam.nl >
    wrote:
    Hey hi....
    >
    I get this weird inconsistency in Firefox using floats.
    >
    I made this little demo of it wich u can find here:

    >
    Now the ? Question mark should be in the grey bar, as it is in Safari and
    Opera however in FF it's floating beneath it.
    >
    Anybody know of a workaround / fix?
    >
    First things first. Why don't you first fix up all the errors.
    Use the W3C validation service. Using one id more than once on a
    page, not closing things properly. Take a look.

    btw, I suggest you use 4.01 Strict.

    --
    dorayme

    Comment

    • Wouter

      #3
      Re: FF -&gt; Safari/Opera Float inconsistency

      Fixed, but the problem remains...


      On 15-08-2007 11:21, in article
      doraymeRidThis-A76AF1.19213215 0820...usnet.co m.au, "dorayme"
      <doraymeRidThis @optusnet.com.a uwrote:
      In article <C2E88B94.1076F %stop@spam.nl>, Wouter <stop@spam.nl >
      wrote:
      >
      >Hey hi....
      >>
      >I get this weird inconsistency in Firefox using floats.
      >>
      >I made this little demo of it wich u can find here:
      >http://tweed.xs4all.nl/demo/fffloats/
      >>
      >Now the ? Question mark should be in the grey bar, as it is in Safari and
      >Opera however in FF it's floating beneath it.
      >>
      >Anybody know of a workaround / fix?
      >>
      >
      First things first. Why don't you first fix up all the errors.
      Use the W3C validation service. Using one id more than once on a
      page, not closing things properly. Take a look.
      >
      btw, I suggest you use 4.01 Strict.

      Comment

      • rf

        #4
        Re: FF -&gt; Safari/Opera Float inconsistency


        "Wouter" <stop@spam.nlwr ote in message news:C2E894FF.1 07E5%stop@spam. nl...
        Fixed, but the problem remains...
        FF is getting it right.
        Floated elements must be positioned (in the source) _before_ the content
        that flows around them.

        Don't use XHTML.
        Don't use transitional.
        Use HTML 4.01 strict. Google for details.

        --
        Richard.


        Comment

        • Wouter

          #5
          Re: FF -&gt; Safari/Opera Float inconsistency

          Tx, changing the position did help.

          Now on the xhtml/html discussion, can I use self closing tags like in xhtml?

          Or do I have to plough thru all my files removing the />'s?




          Comment

          • Rik

            #6
            Re: FF -&gt; Safari/Opera Float inconsistency

            On Wed, 15 Aug 2007 12:55:06 +0200, Wouter <stop@spam.nlwr ote:
            Tx, changing the position did help.
            >
            Now on the xhtml/html discussion, can I use self closing tags like in
            xhtml?
            No.
            Or do I have to plough thru all my files removing the />'s?
            A decent editor can do a search/replace in all files quite quickly.
            --
            Rik Wasmus

            Comment

            • Ben C

              #7
              Re: FF -&gt; Safari/Opera Float inconsistency

              On 2007-08-15, rf <rf@invalid.com wrote:
              >
              "Wouter" <stop@spam.nlwr ote in message news:C2E894FF.1 07E5%stop@spam. nl...
              >Fixed, but the problem remains...
              >>
              FF is getting it right.
              No, FF is getting it slightly wrong I think.
              Floated elements must be positioned (in the source) _before_ the content
              that flows around them.
              Depends what you mean by "before". They cannot go higher than the inline
              content that immediately precedes them [1], although they might end up
              to the left or right of it.

              Provided that they don't go higher, they should be aligned to the top of
              the line box of the inline content preceding them. Requirement [1] isn't
              possible to satisfy if the presence of the float itself causes the line
              to break before the preceding inline content, so in such cases the float
              has to go a line down.

              FF and IE7 both simplify things by always putting the float on the next
              line anyway. Opera and Safari stick closer to the specification however.

              I think that's what we're seeing here.

              It was discussed in more detail here:



              or


              Comment

              Working...