Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Google Microsoft Youtube

Google Denies Altering YouTube Code To Break Microsoft Edge (theverge.com) 135

Earlier this week, a former Microsoft Edge intern alleged that Google deliberately introduced bogus changes to YouTube to break the functionality of the video portal when users on Edge and other browsers tried to access the website. Google today denied the allegation. From a report: Google disputes Bakita's claims, and says the YouTube blank div was merely a bug that was fixed after it was reported. "YouTube does not add code designed to defeat optimizations in other browsers, and works quickly to fix bugs when they're discovered," says a YouTube spokesperson in a statement to The Verge. "We regularly engage with other browser vendors through standards bodies, the Web Platform Tests project, the open-source Chromium project and more to improve browser interoperability." In a statement, Microsoft said, "Google has been a helpful partner and we look forward to the journey as we work on the future of Microsoft Edge."
This discussion has been archived. No new comments can be posted.

Google Denies Altering YouTube Code To Break Microsoft Edge

Comments Filter:
  • by DarkRookie2 ( 5551422 ) on Wednesday December 19, 2018 @02:51PM (#57831426)
    Or at least I think they did.
    Wasn't that old when all that Navigator mess.
    • Or at least I think they did.

      Wasn't that old when all that Navigator mess.

      "YouTube ain't done 'til Edge can't run"?

    • by jellomizer ( 103300 ) on Wednesday December 19, 2018 @03:29PM (#57831628)

      While Netscape wasn't Mr. Standard Complaint. IE, with Active X combined with being installed and integrated in the OS so it couldn't be removed. Is what really got it, more then any coding fault in Netscape.
      Being integrated in the OS, meant the browsers components started up when you booted the OS, and took less foot print, because it was used for other components, (such as the file browser). Active X was faster then Java Applets, because they only ran on Windows so it was just running the application, with the browser replacing window frame.

      Back when PCs were just breaching 200mhz, and 16megabytes of RAM was considered a common amount. Waiting about a minute to load up a browser was common. To have it pop up after a double click was a big deal. And for the Web-Applications to have it run snappy was a big deal too. As on these old system, Running Java Byte Code was a big process.

      Now granted Active-X combined with high level browser OS integration was a long term Stupid idea, because it turned your computer into a pile of goo. Because a bad Active-X control can take over your computer, and via the browser you have access all areas of your OS outside your normal permissions. But at the time, people didn't care about it, because "Why would anyone want to hack me? My computer isn't special"

    • but from what I can tell Microsoft put some hacks in place to post better in benchmarks. Google made some minor changes to Youtube.com (as they're wont to do) and it broke Microsoft's hacks and revealed their actual performance numbers.

      I'm inclined to side with Google on this one, not because I hate Microsoft (I do, but that's besides the point) but because IE and Edge always felt way, way slower than their benchmark numbers would leave you to believe. Like buying one of those $100 GTX 1070s from Alibab
      • but from what I can tell Microsoft put some hacks in place to post better in benchmarks.

        Probably not. It's a common thing for hardware accelerated video playback to be a problem if you need to overlay stuff on top of the video. This basically comes down to: if the video is obscured in any way, neither Google nor Microsoft can use the super optimised hardware path and have to use the hardware decode and compositor rendering path. The difference is Google's browser appears to optimise away empty elements resulting in a non-obscured video where Microsoft's doesn't.

        It happens that optimisations oc

    • MS made sure Windows 3.1 wouldn't run on DR DOS.
  • we believe (Score:5, Insightful)

    by zlives ( 2009072 ) on Wednesday December 19, 2018 @02:56PM (#57831456)

    1. we believe google when they say that they didn't blank microsoft
    2. we believe microsoft that the blank div is the only reason edge was a massive fuckin piece of crap and failed.

    • Re:we believe (Score:5, Insightful)

      by Anonymous Coward on Wednesday December 19, 2018 @03:00PM (#57831478)
      I believe Microsoft suspected Google of playing dirty, because that's exactly what Microsoft would have done.
      • I believe Microsoft suspected Google of playing dirty, because that's exactly what Microsoft would have done.

        I wouldn't put it past any of the big tech firms to play dirty. I'd be shocked if anyone could name a major tech firm that HASN'T played dirty.

        • by Desler ( 1608317 )

          But Google said they would "Do no evil"! How dare you claim they are no different from any other money-grubbing corporation!

          • But Google said they would "Do no evil"!

            That was in their mission statement once upon a time- but didn't they take it out several years ago? They're allowed to do evil now.

          • But Google said they would "Do no evil"! How dare you claim they are no different from any other money-grubbing corporation!

            The official statement was "Don't be evil" which generally allows money grabbing, assuming you are grabbing it fairly with good motives.

          • I'd have to check, but I think google said "Do no evil" as an imperative, not as a description of how they operate.

            "I don't practice what I preach because I'm not the kind of person I'm preaching to."

            - J.R. "Bob" Dobbs

        • I wouldn't put it past any of the big tech firms to play dirty. I'd be shocked if anyone could name a major tech firm that HASN'T played dirty.

          Red Hat?

        • by Dan667 ( 564390 )
          The problem is microsoft has a very very long history of playing dirty. I kind of dismissed their edge optimization complaint when I found out they made it due to their history.
          • by epine ( 68316 )

            Yeah, Microsoft used to pack lead foil into their hockey gloves. Best case, you get a concussion; worst case, you shuffle off this mortal coil.

            Google raps the unprotected part of your arm above the glove with their stick, when they think the referee is looking away. You get a bruise, and continue to play with your head up.

            Brought to you by the Encyclopedia of False Equivalency (and a stick tap from a butter-soft fast path that might very nearly trip over its own skates if they so much as repainted the blue

            • Yeah, Microsoft used to pack lead foil into their hockey gloves. Best case, you get a concussion; worst case, you shuffle off this mortal coil.

              Google raps the unprotected part of your arm above the glove with their stick, when they think the referee is looking away. You get a bruise, and continue to play with your head up.

              OGELT'ORPE!

          • wahhhh. and MS has improved, sometimes voluntarily, sometimes due to legal action. What MS has never done, at least not close to the scale of Google, is sell every bit of data they get about you to damn near anyone who asks. Some telemetry back home is a far cry from direct access to your emails, contacts, personal interests, shopping habits etc.

            America, where no one is ever forgiven for wrongdoing. Corporation or petty criminal, no amount of atonement or punishment is ever enough. Yeah, MS did

            • " What MS has never done, at least not close to the scale of Google, is sell every bit of data they get about you to damn near anyone who asks. Some telemetry back home is a far cry from direct access to your emails, contacts, personal interests, shopping habits etc. "

              No, they only hand it to those we most fear having it. Not corporations, but governments. And telemetry can spy on literally everything you do on your PC, and the EULA gives them the right to do most anything with your data. Trusting Microsoft

      • Re:we believe (Score:5, Informative)

        by Anonymous Coward on Wednesday December 19, 2018 @04:28PM (#57832044)

        Well, it certainly was either incompetence or malice. Google were (actually are) using a non-standard "Shadow DOM v0" model that was only implemented in the Google Chrome browser. On non-chrome, a "polyfill" or pure javascript implementation of that DOM engine was used instead.

        And it's not just Microsoft that are complaining here [cnet.com].

        That's right, all you anti-microsoft blinkered people out there, Mozilla has the same complaint about Google.

        YouTube basically uses an experimental version ("v0") of the shadow DOM API that is officially oboslete before it really got any traction (it's been superceeded by other versions). It was so obsolete that only Chrome implements. it is officially "depcreated [chromestatus.com]" by Google, but we'll see what happens in April 2019.

        • by bob4u2c ( 73467 )
          Your right. . . only IE isn't supporting shadow dom (v0 was experimental, v1 is used now):
          Shadow Dom Support [caniuse.com]

          Now it is being included in the standard Dom/Html/CSS/Event W3C specs.
          W3C [w3.org]


          So yes, YouTube (ie Google) provided a hacked "pollyfill" and/or javascript version to emulate what was spec by W3C but not implemented by IE.
        • Re: (Score:2, Insightful)

          And what has that to do with an *empty* DIV disabling hardware acceleration of video decoding on Edge?

          A video is simply a byte stream, I put it through the decoding API and get frames to display. How the funk can an HTML element have any influence on the decoding happening behind the API? The API does not even know if it is called by a web browser, browser extension or VLC.

          • by Anonymous Coward

            Well, yeah, I did confound this with a different issue--which does still stand though.

            However, to address your point, a transparent div over the video that might be used for text and thus require a different video decoding code path to combine both HTML and Video? Absoultely could because it could be the difference between 'render via GPU into the screen directly' and 'render via CPU into memory for further processing'.

            "The API does not even know if it is called by a web browser, browser extension or VLC.

      • Comment removed (Score:5, Insightful)

        by account_deleted ( 4530225 ) on Wednesday December 19, 2018 @06:31PM (#57832816)
        Comment removed based on user account deletion
        • If you believe either company isn't running on maximum nastiness setting these days?

          I believe a company that has spent the past 2 years endlessly fucking with their UI every other day is covered by Occam's Razor when it comes to some other company's browser not being able to handle a crapy div element.

    • Re:we believe (Score:5, Interesting)

      by DarkRookie2 ( 5551422 ) on Wednesday December 19, 2018 @03:01PM (#57831492)
      I believe neither of them
      Google can't make a webpage properly, and Microsoft can't make a browser.
      • Google is claiming they didn't act willfully, you are ascribing incompetence to them, sounds like you believe them. Me too. Any time Google does something dumb, I have no trouble believing that who ever did it was incompetent given Google's past record with web applications. Most of the ones they have now have problems, and most of the ones they've canned did too.

        The time when we can believe the myth of the superior Google employee has passed, much like the days when we could believe Google wasn't evil.

      • Google can't make a webpage properly

        So you just did believe Google, because that was ultimately their excuse.

        Mind you that's also quite a believable excuse given in the past 2 years the Youtube website probably went a grand total of 7 days in a row without some kind of another busybody UI change. "Oh noes a div element that does nothing but broke our browser, it must be because they hate us and we are perfect at coding in every way! Just don't ask us why we can't handle a div."

    • Comment removed (Score:4, Insightful)

      by account_deleted ( 4530225 ) on Wednesday December 19, 2018 @05:01PM (#57832294)
      Comment removed based on user account deletion
      • Also we have to accept that Google somehow knew that adding a blank DIV would throw a spanner in the works for Edge. We also would have to accept that Google never thought that Microsoft would be able to code around it with an update either.
      • Not just that, but this revelation implies that edge's acceleration features have to be special-cased EVERY TIME. Why? Because this is a trivial case. There is clearly nothing going on that needs to be accelerated in a div that requires no drawing. There is zero defense for the browser choosing to accelerate undrawn elements. Frankly, if the engineer is not a total moron then his only meaningful goal would have been exposing just how poorly this browser is designed. Even if Google did it intentionally, ther

      • Your conspiracy bullshit falls apart when you realize it was not an optimization just for YouTube.

    • Microsoft made no allegations against google whatsoever. A former intern of no importance out of their hundreds of thousands of current and former employees made an off-hand frustrated remark that was probably a joke, and of course the media ran with it to invent newsworthy controversy.

  • by Cowardly Lurker ( 2540102 ) on Wednesday December 19, 2018 @03:01PM (#57831490)

    That's exactly what a saboteur would say!

  • by ChoGGi ( 522069 ) <slashdot@cho[ ].org ['ggi' in gap]> on Wednesday December 19, 2018 @03:02PM (#57831494) Homepage

    This whole thing came from a single hacker news post, and where does it say he's an intern?
    https://news.ycombinator.com/i... [ycombinator.com]

    • by Desler ( 1608317 )

      It comes from his LinkedIn page:

      Software Engineering Intern
      Company NameMicrosoft
      Dates EmployedMay 2018 – Aug 2018
      Employment Duration4 mos
      LocationGreater Seattle Area
      Implemented the background-blend-mode and mix-blend-mode CSS properties in the Edge browser and Windows (C++).
      Wrote web platform standardization tests in HTML, CSS, and JavaScript to verify Edge interoperability. Found bugs in both Chrome and Firefox during this process.

      https://www.linkedin.com/in/jo... [linkedin.com]

  • We need a congressional hearing to prove that it wasn't intentional.

    • I think this was intended as a joke, but yes. We need government at least paying attention to why the number of browsers continues to shrink. We have anti-trust laws, and should enforce them.

      It's possible Google didn't intentionally do this. It seems more likely to me that they did. But we should find out, because monopolies* are bad. And even if they didn't do so intentionally, it probably is worth splitting up Google (and Amazon, and probably MS although that seems less important now.)

      * And so are cl

  • by corezz ( 1603659 ) on Wednesday December 19, 2018 @03:10PM (#57831552) Homepage
    ... does this reporter seriously think Google was ever going to say: "We sure did try to cripple Edge! Guilty as charged! Oh and bring on the anti-trust lawsuits because we don't give a fook."
    • because we don't give a fook.
      Oh, did you want to say: we don't give a fork? Hm, hm ... that sounds martial somehow!

  • by xack ( 5304745 ) on Wednesday December 19, 2018 @03:11PM (#57831554)
    They intentionally disable full screen on youtube videos embedded on web pages in iOS, trying to make the aple experience worse.
    • by mea2214 ( 935585 )
      They also have full screen disabled in Chrome on my Android tablet. They want us to use their youtube app.
    • They intentionally disable full screen on youtube videos embedded on web pages in iOS

      Err no. They disable videos fullscreen embedded on webpages in all browsers, on all platforms where the ebedded iframe doesn't expressly implement allowfullscreen. The fact that Apple's locked down only rendering engine allowed on their platform doesn't implement it properly has nothing to do with the reason they added the option in the first place which was done at the request of the media so they could control the behaviour.

  • Did anyone seem to get this was from a Microsoft Intern who was complaining about this?
    Unless Intern now means something different today. But usually the Intern is the college student who is doing work that the Jr. Developers pawn off on them because the work is too humdrum for them.

    I expect what was happening was Google You Tube service supported a feature, that wasn't in Edge. So someone task the Intern to put that fix into the code to make it work, probably due to it being a simple fix and most likely fr

  • Correct me if I'm wrong. Long time ago Apple and Microsoft did the same thing to each other. IE couldn't open the apple front page and vice versa. A simple [A]Link name href=something[/A] tag didn't work. So don't go and cry about why others do the same thing.
  • Sorry Intern, they didn't have your back...

  • A bug. (Score:5, Funny)

    by QuietLagoon ( 813062 ) on Wednesday December 19, 2018 @03:36PM (#57831644)
    Yup, that's the ticket, a bug. Funny how the bug just happened to affect the performance of a competitor's browser.
    • Nothing funny at all. When someone designs a browser to an artifical benchmark rather than to a webstandard, expect that benchmark to break.

      Or do you somehow doubt that a company that seemingly changes their interface in some way every other fucking weekend (OMG Youtube is black today!) is capable of writing bugs? What do you expect? Regression testing a competitor's browser?

  • TBH, Edge never impressed me. I am saying that as an Edge user for the past 1½ years. To even get to the point of where Edge was "good enough(TM)" took two years of fixing from 2015 to 2017. The number of addons compared to Chrome was ridiculous. I went from Chrome, with thousands of addons, to Edge with a two-digit amount of addons, many of them completely pointless "services" that could be found elsewhere, and many of them duplicates of each others. I still use Edge because it has certain traits that
    • These Microsoft engineers complain a lot about Google websites... Meanwhile a sure way to give Edge a heatstroke on my PC would be to open the emoticon window in a Twitter message. Typically 3-5 icons would be displayed (probably from harddisk cache), and then the CPU went nuts for 30 seconds until I had to recover the webpage, thrashing my message because I wanted to add an emoji. That bug has been there for years now, and Twitter isn't owned by Google. Another example is streaming for a long time on Twitc
  • We regularly engage with other browser vendors through standards bodies,

    That's a pretty low blow. Google is really going after Microsoft's Achilles Heel with that strategy.

  • by The MAZZTer ( 911996 ) <.moc.liamg. .ta. .tzzagem.> on Wednesday December 19, 2018 @03:58PM (#57831808) Homepage
    YouTube shows a lot of stuff on top of the video. Ads, the controls, recommended videos (at the end or when paused), annotations, and so forth. So it's not surprising to see an empty div over the video, since such a div was probably related to one of those items.
  • by Anonymous Coward

    I just had to go back to Chrome because of Firefox not working on a simple Adwords help page. After a few minutes, I gave up and loaded Chrome where the scrollbar magically appeared making the page usable. Not even a complicated page.

  • by Anonymous Coward

    A post on another forum regarding this article from an ex-Google engineer who said he didn't work on YouTube infrastructure said Microsoft's Edge browser's optimizations were very fragile and making small changes to the HTML would slow down page load considerably.

    Another post on the same forum said that unexplainable HTML sequences were used to thwart fraud (e.g. automated scripts) and that invisible divs over video content were a common tactic.

  • "Oops! It was an accident! We never meant to get caught!"

  • Comment removed based on user account deletion
  • good for the goose, good for the gander

  • Google Denies, out now!

    Must be 18 or older.

  • I know I should assess the assertion based on its merits, but "Google denies" really lends it an undeserved credibility.

  • Microsoft Edge, AKA "The Little Browser That Couldn't".

  • We surely can't expect Google to tailor Youtube's behavior to some Edge case; can we?
  • From this story, it looks like Microsoft tooks some "shortcuts" while displaying Youtube video in order to get "better performances"...

    Shortcuts like not actually parsing the whole page but grabbing some specific parts, less to process = running "better"...

    And then google changed youtube page... the parts that Edge used to grab directly were not at the same place anymore and the optimization were lost...

    What could have been the result is Edge showing it's true speed... The speed that could be expected on

  • You ever notice (Score:4, Insightful)

    by nehumanuscrede ( 624750 ) on Wednesday December 19, 2018 @11:14PM (#57834030)

    Anytime a company gets caught doing something stupid these days that it's always a bug, glitch or software error ?
    " Oh, it was a bug. "

    It's like a perfect digital scapegoat where no one has to face any consequences.

    Oh the algorithm accidentally sold all of our stock at .1 instead of 100 dollars a share ?
    " Not our fault, the computer did it ! "

    Oh we accidentally shared all of your personal info online.
    " Bug "

    No matter how epic a problem that gets created, they always go to the same excuse.
    " Bug "

    • Anytime a company gets caught doing something stupid these days that it's always a bug, glitch or software error ?

      The claim: A div tag that was invisible broke our super tuned browser.
      The defense: It was a bug and was removed when reported.
      The context: We are talking about a site that has seen a shitton of UI changes over the past year.

      Occam's Razor: It was a bug, and there's no way Google is regression testing their website on Edge.
      Tinfoil hatter: Google is Teh Evil (TM).

  • Nowadays most people know how to download Chrome to their fresh copy of Windows. For those who don't, the YouTube video "How to download Chrome to your new Windows installation" is actually expected to work properly without a bug.

Make sure your code does nothing gracefully.

Working...