[GH-ISSUE #68] inquiry #140

New issue

Closed

opened 2026-03-13 17:25:21 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 17:25:21 +03:00

Owner

Originally created by @zhang-glitch on GitHub (Jan 30, 2024).
Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/68

Hello, author. At present, it is not only effective to monitor the width and height of the visual area and check the performance by printing. Nothing else works, okay?

Originally created by @zhang-glitch on GitHub (Jan 30, 2024). Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/68 Hello, author. At present, it is not only effective to monitor the width and height of the visual area and check the performance by printing. Nothing else works, okay?

kerem closed this issue

2026-03-13 17:25:27 +03:00

kerem commented

2026-03-13 17:25:32 +03:00

Author

Owner

@AEPKILL commented on GitHub (Jan 31, 2024):

Are you want only enabling performance and viewport checks to verify if devtools is open?

See #64

By the way, viewport checks have been deprecated because they lead to erroneous judgments in many edge cases.

@AEPKILL commented on GitHub (Jan 31, 2024): Are you want only enabling performance and viewport checks to verify if devtools is open? See #64 By the way, viewport checks have been deprecated because they lead to erroneous judgments in many edge cases.

kerem commented

2026-03-13 17:25:38 +03:00

Author

Owner

@zhang-glitch commented on GitHub (Jan 31, 2024):

作者，我的意思是目前除了监听视口宽高，debugger, 打印监听性能这三种方式，其他方式对于chrome来说都不适用了吗？

@zhang-glitch commented on GitHub (Jan 31, 2024): 作者，我的意思是目前除了监听视口宽高，debugger, 打印监听性能这三种方式，其他方式对于chrome来说都不适用了吗？

kerem commented

2026-03-13 17:25:43 +03:00

Author

Owner

@AEPKILL commented on GitHub (Feb 1, 2024):

作者，我的意思是目前除了监听视口宽高，debugger, 打印监听性能这三种方式，其他方式对于chrome来说都不适用了吗？

是的。

对于反调试而言这些检查方式都可以绕过的，只是稍微增加了一点点难度。

@AEPKILL commented on GitHub (Feb 1, 2024): > 作者，我的意思是目前除了监听视口宽高，debugger, 打印监听性能这三种方式，其他方式对于chrome来说都不适用了吗？是的。对于反调试而言这些检查方式都可以绕过的，只是稍微增加了一点点难度。