brownhci/WebGazer

Uncaught (in promise) TypeError: failed to fetch

Open

#260 创建于 2022年6月2日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)HTML (3,412 star) (520 fork)batch import
help wanted

描述

I am trying to run webgazer from an old portable Chromium version (61) on an offline computer (yes, I know it's an odd use case).

When I run the sample webgazer.setGazeListener code from https://webgazer.cs.brown.edu/ I get the error in the title. I am running this on a page served from a local Node.js server. The server doesn't use HTTPS by default, but I thought that might not matter since this is such an old version of Chromium (i.e. before various APIs started only working on secure origins).

I get a prompt to allow access to the webcam (an attached Logitech C920 since it's a desktop), which I allow, but the error still appears. Based on the code at the line number mentioned in the error stack trace (line 148496) it seems like there's an issue getting the stream from the webcam. But the webgazer face overlay canvas is created and I can see myself. However the setGazeListener does not run (doesn't print elapsed time as in example).

贡献者指南

技术栈
javascript
领域
frontendmachine learning
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
JavaScriptWeb APIs (fetch, getUserMedia)WebGazer libraryBrowser version compatibility
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Investigate the error 'failed to fetch' in the WebGazer codebase at the referenced stack trace line (likely around getUserMedia). Check if the issue is caused by using insecure HTTP on an old Chromium version that may enforce secure context for camera access. Review the fetch() call and consider adding error handling for older browsers. Look at the existing comments on the issue for additional context.