• originalucifer
    link
    fedilink
    102
    edit-2
    5 months ago

    this prolly wasnt a bad decision early on… why push something to a population who cant utilize it… but shit changes fast, google.

    • @[email protected]
      link
      fedilink
      English
      505 months ago

      It seems somewhat damning that Google’s own browser had a workaround for this, though

      • originalucifer
        link
        fedilink
        145 months ago

        was it ignorance or malicious intent?

        if it was a person, i would try and assume ignorance… im not sure google the company deserves such respect

        • @[email protected]
          link
          fedilink
          English
          285 months ago

          Or it’s a company so fuckoff huge that one department (Chrome on Android) couldn’t get a bug report escalated in another department (YouTube). Eventually they just put in a UA workaround while the bug rots in a backlog somewhere. Common enterprise bullshit.

          Or the Chrome on Android team didn’t even bother reporting the issue to YouTube and just threw in a cheap workaround. Also common enterprise bullshit.

          • @[email protected]
            link
            fedilink
            English
            8
            edit-2
            5 months ago

            Bingo. When I was a Chrome developer working on video stuff, we mostly treated YouTube like a separate company. Getting our stuff to work with theirs was a priority, but no more than, say, Netflix. We pretty much treated them as a black box that consumed the same API we provided for everyone.

      • ericswpark
        link
        fedilink
        English
        10
        edit-2
        5 months ago

        Could be that the developers for the HiSense TV just copy-pasted whatever UA into their browser codebase and called it a day.