Firefox滚动内部分区中的怪异错误

问题描述

大家好，

我正在构建网站的Firefox中遇到一个非常奇怪的错误。

我特别使用jQuery / GSAP和SmoothScroll，并且在某些手风琴中（内部div），我掌握了很多信息，所以我只为它们设置了固定高度和滚动条（主要网站有默认情况下是隐藏的。）

仅在 FIREFOX 中的手风琴中，它会向下滚动，但是如果您向上滚动，它会继续向下滚动-在控制台日志上使用我找到的滚动方向脚本进行了测试并且总是显示DOWN。

现在这是我的代码：

isChrome = /Chrome/.test(navigator.userAgent) && /Google Inc/.test(navigator.vendor);
// Firefox 1.0+
isFirefox = typeof InstallTrigger !== 'undefined';


if (isChrome) {
  $( '.noscrollz>.vc_tta-panel-body').on( 'mousewheel DOMMouseScroll wheel',function ( e ) {
      var e0 = e.originalEvent,delta = e0.wheelDelta || -e0.detail;
        this.scrollTop += ( delta < 0 ? 1 : -1 ) * 25;
        e.preventDefault();
});
}

if (isFirefox) { 
      $( '.noscrollz>.vc_tta-panel-body').on( 'mousewheel DOMMouseScroll wheel',function ( e ) {
      var e2 = e.originalEvent,delta2 = e2.wheelDelta || -e2.detail;
      this.scrollTop += ( delta2 > 0 ? 1 : -1 ) * 25;
        e.preventDefault();
});
}

我似乎找不到问题，任何人都可以从字面上帮助我，我一直在努力理解过去六个小时的原因。

非常感谢您，希望大家一切安好。

解决方法

编辑：

这完美无瑕（ deltaY 可能是 Firefox 漏洞的原因）。

 Monitors watch logs and check that they behave correctly.  They also
   watch for certificates of interest.

   A monitor needs to,at least,inspect every new entry in each log it
   watches.  It may also want to keep copies of entire logs.  In order
   to do this,it should follow these steps for each log:

   1.  Fetch the current STH (Section 4.3).

   2.  Verify the STH signature.

   3.  Fetch all the entries in the tree corresponding to the STH
       (Section 4.6).

   4.  Confirm that the tree made from the fetched entries produces the
       same hash as that in the STH.

   5.  Fetch the current STH (Section 4.3).  Repeat until the STH
       changes.

   6.  Verify the STH signature.

   7.  Fetch all the new entries in the tree corresponding to the STH
       (Section 4.6).  If they remain unavailable for an extended
       period,then this should be viewed as misbehavior on the part of
       the log.

   8.  Either:

       1.  Verify that the updated list of all entries generates a tree
           with the same hash as the new STH.

       Or,if it is not keeping all log entries:

       2.  Fetch a consistency proof for the new STH with the previous
           STH (Section 4.4).

       3.  Verify the consistency proof.

       4.  Verify that the new entries generate the corresponding
           elements in the consistency proof.

   9.  Go to Step 5.