WebKit Quirks.cpp

>>Bodaci+(OP)
This bit was interesting.

  bool Quirks::requiresUserGestureToPauseInPictureInPicture() const
  {
  #if ENABLE(VIDEO_PRESENTATION_MODE)
      // Facebook, Twitter, and Reddit will naively pause a <video> element that has scrolled out of the viewport,
      // regardless of whether that element is currently in PiP mode.
      // We should remove the quirk once <rdar://problem/67273166>, <rdar://problem/73369869>, and <rdar://problem/80645747> have been fixed.
      if (!needsQuirks())
          return false;

      if (!m_requiresUserGestureToPauseInPictureInPicture) {
          auto domain = RegistrableDomain(m_document->topDocument().url()).string();
          m_requiresUserGestureToPauseInPictureInPicture = domain == "facebook.com"_s || domain == "twitter.com"_s || domain == "reddit.com"_s;
      }
  
      return *m_requiresUserGestureToPauseInPictureInPicture;
  #else
      return false;
  #endif
  }

>>babelf+e8
The first rule of browser development is "forget the standard, forget consistency... If it's popular and works in other browsers but not yours, your browser is broken."

>>shadow+hk
Might as well create site-specific browsers.

>>matheu+Oz
It’s getting closer to the point where we call the entire current “web” a Google-specific network, Google Chrome is renamed a “Google” browser instead of a web browser, and we re-make a new interlinked network which does not require one specific company’s product to use. (Never mind an advertisement company.)

The “Google” network and sites can be kept on as a necessary evil proprietary service, like Facebook is for many, and also LinkedIn.

>>teddyh+ZO
That sounds like requesting an awful lot of volunteer labor from web developers who don't want to do that.

Web developers, ultimately, have very little vested interest in what browser is winning or who's using what as long as (a) people can access their site and (b) they don't have to write the site twice. That's their incentive model. Telling them that the spec is X and if Google does Y Google is wrong when Google is like 90% market share is just kind of a funny idea for them to laugh at and then go right back to solving the problem in a way that reaches 90% of the possible users (and then maybe, time permitting, writing pieces of the site twice to pick up a fraction of the remaining 10%).

>>shadow+vP
Those people are then, to further the analogy, not “web” developers but “Google network” developers. Therefore, I would not ask them to do anything more than they are doing; what they are doing is irrelevant to the new interlinked network.

>>teddyh+jP2
Which is fine. I'm sure they will care when the new interlinked network becomes relevant to anyone for anything.

(If one wants to do that road, one should probably start reasoning from the "killer app" of a novel network model. The killer app of the web was HTML, and specifically the hyperlink combined with the URL, which allowed for association of information in a way that hadn't been possible before. It'll be hard to one-up that, but if someone could find a way to do it that would be hard for HTML to just grow to consume, there may be room for a novel information service).

zlacker