• RogueBanana@lemmy.zip
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    1 year ago

    That’s a weird take. Default caters for majority users in most cases, so ofc they would be prioritised as it should be.

    • Sithuk@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      15
      ·
      edit-2
      1 year ago

      The current default single click will no longer be default. Development testing tends to focus on the default settings. That means there is a higher risk of a bug slipping through to the users who choose to continue using single click. The situation is unfortunate for those who prefer single click. Not sure why that is a weird take?

      • sky@codesink.io
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        2
        ·
        1 year ago

        Because double-clicking has worked fine for decades despite not being the default. You should relax.

      • RogueBanana@lemmy.zip
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Because you think you should be given priority when you know you’re in the minority that’s why. Was trying to be subtle about it but ig it didn’t come through. I do know how QA works and ik it should be focused for majority first from features to bug fixes. This little change isn’t gonna make a big difference anyway given how minor it is so I don’t see why this is so much of a concern.

      • mnemonicmonkeys@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        That means there is a higher risk of a bug slipping through to the users who choose to continue using single click.

        The same can be said about double-clicking with the old defaults. Which is arguably worse since said bugs will affect more people