Everything worked perfectly as it always does.

  • Tanoh@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    10 months ago

    There are quite a lot of quirks with how browser (or rather rendering engines) interpret CSS, and in quite a few places the spec is ambiguous. So there is no “correct” way of implementing it.

    But, this is either just them being lazy or bad mangement.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      10 months ago

      Do you have an example of a quirk where Chrome and Firefox treat something in the spec differently? I haven’t seen that in a while.