Greasy Fork is available in English.
在 Netflix 上开启最佳音视频质量和更多功能
Userscripts can't directly intercept network requests, so Netflix Plus needs to hook into execution before the <script> tag runs to prevent multiple player instances. Since the script tag is placed near the top of the <body>, triggering the userscript via document-body happens too late. This delay significantly reduces overall stability and may lead to memory leaks or even more serious issues.
Userscripts can't directly intercept network requests, so Netflix Plus needs to hook into execution before the
<script>tag runs to prevent multiple player instances. Since the script tag is placed near the top of the<body>, triggering the userscript viadocument-bodyhappens too late. This delay significantly reduces overall stability and may lead to memory leaks or even more serious issues.
Are you sure? I have been running it without any of the mentioned issues when running document-body.
I also made a cleaned up version of the script that I use separately (e.g. when I disable the default script) that uses "document-start" that works 100% of the time without issue, like what happens with ViolentMonkey on the default version of this script, which causes it to not initiate correctly.
There must be something here.
Question/feature request for the DEV.
Could support for ViolentMonkey be looked into and added for this script. I have found that changing the
"// @run-at document-start"
to
"// @run-at document-body", or "// @run-at document-end", or "// @run-at document-idle"
allows for the script to seemingly work almost perfectly except you don't seem to get the right click menu. For the menu you have to still click on the extension itself, which does show the whole script and every option there. All the options besides the bit rate option still seem to perform correctly, at least from my tests.
I would like the dev of the script to see if they get the same results, and if this is something they could do.