3 ms·

Wouldn't this make it even worse? It worked correctly, then they changed it to _not_ work for their sites?

• Arnt 6y ago
  The source is public and the version history too, so you don't need to assume, you can look. If you don't see anything particular, you may assume that it's a bug and wasn't easily visible to the developers either.
  • fblifeadvice645 6y ago
    This will most likely be a patch the product bits pf Chrome, not chromium. The bug isn't in Edge.
    • burnerfi5724 6y ago
      https://chromium.googlesource.com/chromium/src.git/+/f800edbd1b50ecc13a0d3391f5f45ba9c84625be%5E%21/#F0 https://chromium.googlesource.com/chromium/src.git/+/f800edb... Here's the fix, the bug is in chromium but only affects chrome because it has some "Hosted Apps" installed out of the box.
  • zelphirkalt 6y ago
    You are talking about Chrome or Chromium?
    • Arnt 6y ago
      When I looked at the source, around 2015, there wasn't much difference, other than the name. People called "Google" were allowed to name the result of building it "Chrome". If you weren't Google you had to call it Chromium, and could of course apply patches or change the build flags. The functional differences I saw then were all a result of patches that were applied by my distribution.