• andioop
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 days ago

    thanks, this is the stuff I keep my programming.dev account for

  • fox2263@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 days ago

    Since CSS has changed so much that there are old and new ways of doing things, maybe they should have changed version numbers.

      • lambalicious@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago
        div.mydiv {
          template <Variable mycolor> 
          requires std::is_named_color<mycolor> || is_function_color<mycolor> || is_hexa<mycolor>
          mydiv& background-color: mycolor 
          noexcept( noexcept( background-color: mycolor) || !std::is_IE6 )
          --> decltype (css_declaration<property>)
          ;
        }
        
      • Kissaki
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        Please make them incompatible so that I have to upgrade.

    • Kissaki
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      To what end? What would you expect version numbers to do? How would you specify or use them, which what consequences?

      Grouping changes into releases with explicit numbering instead of a living standard with generic @supports checks?

      I guess it would make some things easier and more obvious.

    • MimicJar@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      2 days ago

      Each snippet clearly states which browsers+version supports it (as well as a general year if all major browsers support it). At a quick glance, with the exception of trying to find an unsupported on Firefox snippet, everything seemed supported by all major browsers.