Don't use fudge factor for buffered ranges when seeking.

Chrome doesn't seem to support gap jumping immediately after a seek.
So when we detect how much is buffered after a seek, we should use the
exact ranges.  Otherwise we will be left with a small gap that Chrome
doesn't want to jump.

Issue #655

Change-Id: I2d853e0c2b95285013463f38cece56ea9ea56133

Author: TheModMaker

lib/media/streaming_engine.js

@@ -545,9 +545,11 @@ shaka.media.StreamingEngine.prototype.seeked = function() {
       continue;
     }
 
+    // Don't use a fudge factor here since Chrome doesn't jump gaps after a seek
+    // https://github.com/google/shaka-player/issues/655
     var playheadTime = this.playhead_.getTime();
     var bufferedAhead = this.mediaSourceEngine_.bufferedAheadOf(
-        type, playheadTime, 0.1);
+        type, playheadTime);
     if (bufferedAhead > 0) {
       // The playhead has moved into a buffered region.
       shaka.log.debug(logPrefix,