Firefox 1.0 and :after

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

    Firefox 1.0 and :after

    I've just noticed something strange in Firefox 1.0: it seems that the
    :after pseudo-element doesn't work as well as it used to.

    Have a look at: http://www.relinquiere.com/test1.html

    This is a simple list (ul) of images: I would like to display the titles
    of these images using generated content, so I used a simple rule:

    img:after { content: attr(title) ; }

    but this doesn't work.

    :after is still understood, though, as you can see at
    http://www.relinquiere.com/test3.html where I generate a fixed string
    after the li element. This works.
    The cause is not the dynamic generated content either: in
    http://www.relinquiere.com/test4.html, I use content: attr(title) on the
    li element and it still works.

    In http://www.relinquiere.com/test2.html, I tried to generate a fixed
    string after the img, to no avail. So the problem seems to come from
    mixing :after and generated content on the img element...

    Isn't it weird? Or am I doing something wrong? All this used to work up
    to Firefox 0.8 (and it still works in Opera 7), so is it a bug in Firefox?

    As a sidenote, in test3 and test4, I display the generated content using
    the "block" mode, but it appears just next to the image. I would expect
    it to be under the image (or the li), as it used to...


    Thanks for your help,

    Vincent.


    --
    Want to spend holidays in France ? Check http://www.relinquiere.com/
  • Vincent Poinot

    #2
    Re: Firefox 1.0 and :after

    Vincent Poinot wrote:[color=blue]
    > I've just noticed something strange in Firefox 1.0: it seems that the
    > :after pseudo-element doesn't work as well as it used to.
    >
    > Have a look at: http://www.relinquiere.com/test1.html
    >
    > This is a simple list (ul) of images: I would like to display the titles
    > of these images using generated content, so I used a simple rule:
    >
    > img:after { content: attr(title) ; }
    >
    > but this doesn't work.
    >
    > :after is still understood, though, as you can see at
    > http://www.relinquiere.com/test3.html where I generate a fixed string
    > after the li element. This works.
    > The cause is not the dynamic generated content either: in
    > http://www.relinquiere.com/test4.html, I use content: attr(title) on the
    > li element and it still works.
    >
    > In http://www.relinquiere.com/test2.html, I tried to generate a fixed
    > string after the img, to no avail. So the problem seems to come from
    > mixing :after and generated content on the img element...
    >
    > Isn't it weird? Or am I doing something wrong? All this used to work up
    > to Firefox 0.8 (and it still works in Opera 7), so is it a bug in Firefox?
    >
    > As a sidenote, in test3 and test4, I display the generated content using
    > the "block" mode, but it appears just next to the image. I would expect
    > it to be under the image (or the li), as it used to...
    >
    >
    > Thanks for your help,
    >
    > Vincent.
    >
    >[/color]

    Nobody, really?
    Don't you experience the same problems?

    --
    Want to spend holidays in France ? Check http://www.relinquiere.com/

    Comment

    • phil_gg04@treefic.com

      #3
      Re: Firefox 1.0 and :after

      Vincent,

      I looked at your example and as you report is doesn't work in FF1.0.
      It also doesn't work in Mozilla 1.8b, but does work in Opera 8b. I
      can't see anything obvious wrong with your code, but I have never used
      :before/:after or content so I may have missed something. I have
      looked in bugzilla but can't find anything obvious. I suggest that you
      create an even smaller test case and file it in bugzilla; the Mozilla
      developers will tell no doubt find what you're doing that is causing
      the problem.

      --Phil.

      Comment

      • Lukasz Grabun

        #4
        Re: Firefox 1.0 and :after

        On Sat, 26 Feb 2005 13:07:28 +0100, Vincent Poinot wrote:
        [color=blue]
        > This is a simple list (ul) of images: I would like to display the titles
        > of these images using generated content, so I used a simple rule:
        > img:after { content: attr(title) ; }[/color]

        OK, this is not of much help, I guess, but :after seems to work fine
        with links, for example on this site: http://justinfrench.com/
        It looks alright on my FF 1.0/Linux. Can't help you more, however.

        Comment

        • Vincent Poinot

          #5
          Re: Firefox 1.0 and :after

          phil_gg04@treef ic.com wrote:[color=blue]
          > Vincent,
          >
          > I looked at your example and as you report is doesn't work in FF1.0.
          > It also doesn't work in Mozilla 1.8b, but does work in Opera 8b. I
          > can't see anything obvious wrong with your code, but I have never used
          > :before/:after or content so I may have missed something. I have
          > looked in bugzilla but can't find anything obvious. I suggest that you
          > create an even smaller test case and file it in bugzilla; the Mozilla
          > developers will tell no doubt find what you're doing that is causing
          > the problem.[/color]

          Thanks for looking, I wanted to be sure I had not made a silly
          mistake... So I guess I can follow your advice and file a new bug.

          Vincent.


          --
          Want to spend holidays in France ? Check http://www.relinquiere.com/

          Comment

          • Barbara de Zoete

            #6
            Re: Firefox 1.0 and :after

            On Tue, 01 Mar 2005 22:45:58 +0100, Vincent Poinot
            <vincent.use-my-last-name-here@wanadoo.fr > wrote:
            [color=blue]
            > phil_gg04@treef ic.com wrote:[/color]
            [color=blue][color=green]
            >> I looked at your example and as you report is doesn't work in FF1.0.[/color]
            >
            > Thanks for looking, I wanted to be sure I had not made a silly mistake... So I
            > guess I can follow your advice and file a new bug.
            >[/color]

            I'm not sure it is a bug. In no way is a browser developer oblidged to implement
            any CSS feature at all, and if he does, there is no law that sais 'You _have_ to
            implement a feature to its full extend'.


            --
            ,-- --<--@ -- PretLetters: 'woest wyf', met vele interesses: ----------.
            | weblog | http://home.wanadoo.nl/b.de.zoete/_private/weblog.html |
            | webontwerp | http://home.wanadoo.nl/b.de.zoete/html/webontwerp.html |
            |zweefvliegen | http://home.wanadoo.nl/b.de.zoete/html/vliegen.html |
            `-------------------------------------------------- --<--@ ------------'

            Comment

            • Vincent Poinot

              #7
              Re: Firefox 1.0 and :after

              Barbara de Zoete wrote:[color=blue]
              > On Tue, 01 Mar 2005 22:45:58 +0100, Vincent Poinot
              > <vincent.use-my-last-name-here@wanadoo.fr > wrote:
              >[color=green]
              >> phil_gg04@treef ic.com wrote:[/color]
              >
              >[color=green][color=darkred]
              >>> I looked at your example and as you report is doesn't work in FF1.0.[/color]
              >>
              >>
              >> Thanks for looking, I wanted to be sure I had not made a silly
              >> mistake... So I guess I can follow your advice and file a new bug.
              >>[/color]
              >
              > I'm not sure it is a bug. In no way is a browser developer oblidged to
              > implement any CSS feature at all, and if he does, there is no law that
              > sais 'You _have_ to implement a feature to its full extend'.
              >
              >[/color]

              You may be right, but the point is that this feature used to be
              implemented in older versions of Firefox (try 0.8 if you still have it).
              So if it is not a bug, strictly speaking, there is at least some
              regression involved...

              --
              Want to spend holidays in France ? Check http://www.relinquiere.com/

              Comment

              • Pierre Goiffon

                #8
                Re: Firefox 1.0 and :after

                phil_gg04@treef ic.com wrote:[color=blue]
                > I can't see anything obvious wrong with your code[/color]

                The CSS validator seems to be OK with it indeed :
                <http://jigsaw.w3.org/css-validator/validator?profi le=css2&warning =2&uri=http%3A//www.relinquiere .com/test1.html>

                And Firefox view this page in standard compliance mode... This is strange

                Comment

                • JP. Baker

                  #9
                  Re: Firefox 1.0 and :after

                  In article <4224ec1e$0$312 8$8fcfb975@news .wanadoo.fr>,
                  Vincent Poinot <vincent.use-my-last-name-here@wanadoo.fr > wrote:[color=blue]
                  >Barbara de Zoete wrote:[color=green]
                  >>
                  >> I'm not sure it is a bug. In no way is a browser developer oblidged to
                  >> implement any CSS feature at all, and if he does, there is no law that
                  >> sais 'You _have_ to implement a feature to its full extend'.
                  >>[/color]
                  >
                  >You may be right, but the point is that this feature used to be
                  >implemented in older versions of Firefox (try 0.8 if you still have it).
                  >So if it is not a bug, strictly speaking, there is at least some
                  >regression involved...[/color]

                  RESOLVED (dbaron) in Core - CSS Parsing and Computation. Last updated 2010-07-27.



                  nhoJ
                  --
                  John P Baker

                  Comment

                  • Vincent Poinot

                    #10
                    Re: Firefox 1.0 and :after

                    JP. Baker wrote:[color=blue]
                    >
                    > https://bugzilla.mozilla.org/show_bug.cgi?id=245633
                    > https://bugzilla.mozilla.org/show_bug.cgi?id=169334
                    >[/color]

                    Ok, so it's essentially a very unstable feature...
                    Too bad.

                    --
                    Want to spend holidays in France ? Check http://www.relinquiere.com/

                    Comment

                    • kchayka

                      #11
                      Re: Firefox 1.0 and :after

                      Pierre Goiffon wrote:[color=blue]
                      > phil_gg04@treef ic.com wrote:
                      >
                      > The CSS validator seems to be OK with it indeed :
                      > <http://jigsaw.w3.org/css-validator/validator?profi le=css2&warning =2&uri=http%3A//www.relinquiere .com/test1.html>[/color]

                      The CSS validator does not check that properties are applied to
                      appropriate elements, it only checks syntax.

                      The syntax itself is valid. That doesn't mean the rule is logical.

                      --
                      Reply email address is a bottomless spam bucket.
                      Please reply to the group so everyone can share.

                      Comment

                      Working...