Greasy Fork镜像

ENABLE_NO_SMOOTH_TRANSFORM = false 的時候聊天框裏面的messages會不見，AI chat summary 也不會顯示，狀況截圖在附件。聊天框本身沒其他問題。其他設定都是預設值。 用的是 Chromium Edge 126.0 + Tampermonkey

更正。AI chat summary 沒問題，能夠正常顯示。

不要改 ENABLE_NO_SMOOTH_TRANSFORM

不要擅自改了某些設定然後回報有問題。你可以選不評分進行回報

修正了。請修改評分

這次的問題是 SUPPRESS_refreshOffsetContainerHeight_ (在2月新增，避免裡面讀clientHeight拖慢運行），會跟ENABLE_NO_SMOOTH_TRANSFORM = false 發生衝突

這腳本那堆true false 選項都是為了每次 YouTube更新時能作DEBUG用。一般不用修改。

有時候功能已變得無效時，會直接改成false封印起來。那些的話改成true反而會無法正常運作

Bug已確認修正。 評分已修改。

The script usually works and the performance improvement is very substantial. However, the chat would sometimes stop scrolling and occasionally fail to load new messages, even without user interaction. This is can be manually triggered consistently by seeking with the chat open, both by using the mouse to drag the playback progress bar and by using the keyboard shortcuts to rewind/fastfoward (including the number keys).

(Script version 0.102.15 tested on Edgium 138 with ViolentMonkey 2.31.0, default everything, no other scripts or extensions.)

The script usually works and the performance improvement is very substantial. However, the chat would sometimes stop scrolling and occasionally fail to load new messages, even without user interaction. This is can be manually triggered consistently by seeking with the chat open, both by using the mouse to drag the playback progress bar and by using the keyboard shortcuts to rewind/fastfoward (including the number keys).

(Script version 0.102.15 tested on Edgium 138 with ViolentMonkey 2.31.0, default everything, no other scripts or extensions.)

I believe I experienced this before but I cannot find a way to reproduce.

This could be related to the message component re-using (otherwise the memory will grow along with the streaming)

If you find a way to reproduce this issue easily, I can help fixing.

I have noticed that, you are using Edge 138.

Violentmonkey is an old MV2 extension.

I would suggest you switch to ScriptCat or Tampermonkey to test again.

PS. Tampermonkey is closed source

I am doing fixing and improvement for ScriptCat recently. ScriptCat shall have no issue of running this script in Edge 138.

I switched to ScriptCat as you suggested. However, the issue has persisted, and can still be reproduced consistently with the methods described above. After further testing, it appears that the issue is not present on Chrome 138 or Firefox 140 but is 100% consistent on Edge 138/139 and Brave 138, this is true regardless of the script manager used. Perhaps this is an issue with chromium.