Hey there - first of all, I love vose.tv, I use it almost every day.
I noticed recently that the Youtube embedded channel icon/title/watch later/share header that shows when you hover over a video (shown below) disappears after you switch the video to anything other than the initial video.
This happens regardless of if the video progresses automatically after the first one finishes or if you manually move it to a new video. It also does come back if you go back to the first video in the playlist. Here's what it looks like once it disappears. Notice that the mouse is hovering over the video in the screenshot:
I tried this across 2 different windows machines on both Chrome and Edge and saw the same problem.
As a side issue unrelated to this, I thought I'd clone your repo and see if I could poke around and figure it out myself. After cloning, installing the dependencies, renaming the .env-sample file to .env and starting the server it looks like it can't find the client css file:
I hardcoded the main.css file to load from /src but after doing that I just get an error in the terminal while the browser hangs:
listening at http://localhost:3000
Recursive Videos Error TypeError: Cannot read property 'children' of undefined
at children (C:\vose.tv\src\services/fetch-subreddit.js:63:22)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:4104) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined
at require.app.use (C:\vose.tv\src/main.server.js:90:24)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:4104) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an
async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 39)
(node:4104) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that ar
e not handled will terminate the Node.js process with a non-zero exit code.
Sorry, I know that's two separate things. I just didn't think the setup stuff was worth its own issue.
Hey there - first of all, I love vose.tv, I use it almost every day.
I noticed recently that the Youtube embedded channel icon/title/watch later/share header that shows when you hover over a video (shown below) disappears after you switch the video to anything other than the initial video.
This happens regardless of if the video progresses automatically after the first one finishes or if you manually move it to a new video. It also does come back if you go back to the first video in the playlist. Here's what it looks like once it disappears. Notice that the mouse is hovering over the video in the screenshot:
I tried this across 2 different windows machines on both Chrome and Edge and saw the same problem.
As a side issue unrelated to this, I thought I'd clone your repo and see if I could poke around and figure it out myself. After cloning, installing the dependencies, renaming the .env-sample file to .env and starting the server it looks like it can't find the client css file:
I hardcoded the main.css file to load from /src but after doing that I just get an error in the terminal while the browser hangs:
listening at http://localhost:3000
Recursive Videos Error TypeError: Cannot read property 'children' of undefined
at children (C:\vose.tv\src\services/fetch-subreddit.js:63:22)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:4104) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined
at require.app.use (C:\vose.tv\src/main.server.js:90:24)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:4104) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an
async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 39)
(node:4104) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that ar
e not handled will terminate the Node.js process with a non-zero exit code.
Sorry, I know that's two separate things. I just didn't think the setup stuff was worth its own issue.