FF, Rewind and Timeline not working in Chrome, Windows 11

#1

I have two Windows 11 computers running Windows 11, running Channels DVR with Chrome version 142.0.7444.135. Fast Forward buttons do nothing and the Timeline for the recorded program doesn't appear. Everything works fine in Edge and on my Android phone. It's only a problem with Chrome in Windows 11. I've tried clearing all history, cache and cookies. Running Channels with a link to my Channels DVR Server. I've looked at other threads with similar problems but not seeing a solution for Chrome. Any ideas on how to fix this?

Thanks,
Gary

image

#2

Are you aware that the web browser view is an administrative interface and not officially supported for viewing? I just tested and both forward and back work yet slowly. You may be happier using the slider on the timeline.

#3

Hi Morris,
Thanks for the reply. I use the Channels app on other devices, but what do you use on Windows PCs other than the web browser? On Chrome, the buttons don't work at all and the timeline slider doesn't even appear. It's just not there. As I said above, it works fine on Edge. It used to work in Chrome for me, but something has changed.

#4

The test I did before posting was done on Chrome for windows. You may need to click the video to see the slider. An option to view on windows is to install an android client or emulator. I've had good luck using BlueStacks. The android client runs well on it

#5

No slider, clicking the video is like clicking pause/play. I think the slider, rewind and FF button issues are related. Just don't know how to get them back.

#6

It may be a browser extension. Try incognito mode to test that

#7

You were right on about browser extensions! So this is weird. Disabled all extensions and the DVR works! Trying to determine which extension actually caused the issue, re-enabled one by one. All enabled now, and it's still working! May never know which one was the cause unless it happens again. Anyway, thanks very much for your help!

#8

Glad you are functional again. Possibly there was an extension update

#9