1.0.7

Fix YouTube shuffle info getter

Full Changelog: 1.0.6...1.0.7

1.0.6

Fix an issue with the YouTube "next" bang.

1.0.5

Fix the flickering issue on the options page.

Add an option to skip through "chapters" on YouTube videos using the Next/Previous bangs...

• The Next bang will seek to the start of the next chapter (if one exists) instead of advancing to the next video. The same with the Previous bang.
• This feature is optional so you'll have to go to the options page to enable it.
• Chapters are timestamp anchor links (like 7:41) that jump to specific locations in the video. They can sometimes be seen in the progress bar.
• Chapters can come from a few different sources, prioritized by usefulness:
  1. Timestamps that were explicitly written in the video description by the video's author.
  2. Timestamps that users added in comments. These are less reliable but still better than nothing.
     • If there are multiple comments with lists of timestamps, we use the one with the longest list.
  3. Timestamps generated automatically by YouTube's AI.
     • These appear in the bottom of the description (when expanded) as "Moments"
     • They are usually accurate for long videos, so we use them for videos longer than 15 minutes.
• Chapters will only be used if more than 2 timestamps are found.
• If there is no next timestamp (i.e., no timestamp later than the current time), the Next bang behaves as normal, advancing to the next video.
• The same with the Previous bang.

Full Changelog: 1.0.4...1.0.5

1.0.4

Fix an issue where the YouTube play state was disrupted when mousing over certain elements.

Full Changelog: 1.0.3...1.0.4

1.0.3

Update YouTube functions.

1.0.2

Update YouTube functions

1.0.1

Update Netflix script

1.0.0

Sweet new update! Automatically send info updates to Rainmeter when the user successfully activates a command. Normally, after executing a bang through your skin, you'd have to wait for the extension's info watcher to pick up on changes to the site. That's not a big deal when you have the tab open, since it checks for changes every 50ms. But timeouts and intervals in background tabs are throttled, so the update rate is drastically reduced (e.g., once per second in Firefox).

For example, after passing the Pause bang to a background tab, it would take up to 1 second for your skin's play/pause button to update to reflect the fact that the video was paused. But we can just send updated info as part of executing the Bang. So, as of v1.0, when the extension receives the Pause bang from Rainmeter and goes about pausing the video through JavaScript APIs, it immediately sends Rainmeter new information indicating that the video is now paused. That means Rainmeter's state will update instantly. And then, how soon it visually updates just depends on your skin's Update properties.

Previously, there was an autoconfig script for Firefox on this repo that served a similar purpose. Basically, it dynamically configured the timeout throttling amount based on whether this extension was handling any media playback on a compatible website. This was a kind of silly workaround, compared to the new method. I honestly have no idea why I didn't think to do it earlier, it's so obvious.

So, in any event, WNPCListener.js is now kind of obsolete. It's been removed from the repo. There are still some situations where it might be useful, though. As mentioned, this new method sends instant updates when a bang is fired. Besides that, it updates at the normal interval of 50ms, which may be throttled if the tab is in the background. So if any info changes naturally (e.g., due to playback naturally finishing and moving to the next media in a playlist), the extension will pick that up at the normal rate. So if the tab is in the background, there may be a noticeable delay in Rainmeter updating its meters.

WNPCListener.js would reduce that delay to 50ms max. But it may come at a hefty cost. After all, these things are throttled in background tabs for a good reason. And there's no way to make it apply only to the tabs we're operating on. It's a global thing. The main reason I wrote that script was so that meters would update as soon as I triggered a bang. For example, if I click my Pause button, the video will instantly pause, so the Pause button should immediately change to a Play button. I'm less concerned about the speed of detecting natural changes, since there's more wiggle room there. Delays are a lot more noticeable when they involve user input. So, I don't think WNPCListener.js is worth it anymore, but you're free to continue using it if you want. It will still work in v1, at least for now.

0.9.8

Fix the repeat method on YouTube queues/mixes etc.

0.9.7

Use a more reliable method of searching for top-level buttons to check/click. This should eliminate some debug error messages on queue lists, etc.