Sean Feng
Sean Feng
Yup exactly ^! Basically just remove the requirement of `--firefox.geckoProfilerParams.features "screenshots"`
I want to +1 to what Dan said in the WebPerfWG that resource timing seems to be a more appropriate place for this. I assume we can't use existing timing...
So..what if we just do what the current spec expects? Like we don't expose the iframe request if it's aborted and if it doesn't, we expose it along with TAO...
I don't know the details but first of you could try running the command with debug mode `curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh | DOCHAT_DEBUG=true bash` and see if you can get more...
I think starting with [this commit](https://github.com/huan/docker-wechat/commit/ba83bb4eff99749f376e4545961a10e0245dd671), we start to try to run the container with GPU access. Perhaps you could try to modify the script locally by removing those lines...
@Jiawens @frankmanbb Have you tried to install `nvidia-container-toolkit` as what @qinenergy pointed?
@emilio Emilio, do you have thoughts about this since in the past we had tried to done something similar for ``?
Does the spec cover the case where service worker synthesizing a response, so the synthesized response shouldn't be blocked by ORB if service worker's request passes?
I am working on the Firefox implementation, and I agree with https://github.com/whatwg/html/pull/8174#issuecomment-1234875771 from Joey.
@domenic Yeah, I fixed them and it's https://github.com/web-platform-tests/wpt/pull/36449. I need to figure out why it's not automatically merged.