Skip to content

Releases: CODESIGN2/media-playback-speed

Confirms compatibility with WordPress 6.0

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 05 Jul 08:54
e416968

Just an update for WordPress.org

Confirms compatibility with WordPress 5.9

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 19 Feb 16:49
f79cc71

Just a routine update so that WordPress.org knows the plugin has been tested with WordPress 5.9.

Troubleshooting speed setting in WP

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 03 Sep 04:48
6f53d6e
1.2.0

Update readme.txt

More graphics iteration

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 20 Oct 15:05

Just updates graphics so the logo is not a resized 128px, and it reflects the 2x max of this plugin out of the box. Of course people are still free to write sibling plugins with other speeds, and CSS options etc.

This also adds the GIMP source assets for editing as I rushed the graphics to just not be the default.

This also tests 10up ignoring the GIMP files. I'll check SVN when done using plugin directory link.

Fix Daron name

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 20 Oct 12:20
1.1.8

Correctly spell Daron name

Plugin Directory Graphics

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 20 Oct 12:15

This should (hopefully) deploy graphics for this plugin finally so that it looks a bit better in the plugin directory.

Compatibility check with 5.5.1

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 20 Oct 11:44
cb918f4

No actual code changes. Just manually verified the plugin still works with 5.5.1

Fix small oversight

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 09 Nov 22:55

The prior 1.1.4 release accidentally made all speed controls global by not performing a check correctly.

There are 3 things

  1. All shortcode controls are specifically for those shortcodes.
  2. If static HTML controls are present without an aria-controls HTML attribute or with an invalid aria-controls, then they are page global
  3. If static HTML controls are present with an aria-controls HTML attribute which is valid, then they are non-global, and only affect a single element, which may be media-element-js or simply HTML5 audio or video tags

I cannot imagine why you would use custom HTML for media-element-js, but if you did, then you might want to also filter the playback speeds to remove on-widget controls. It's entirely up to the site-admin.

Global controls also change the instance controls right now. I may be open to revising this if it's needed for some super-odd control over media.

Improved Gutenberg & non mediaelement-js support

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 09 Nov 22:33

This release improves on JS non-mediaelement-js support

the following HTML code was added to a custom HTML block

<div class="page-playback-speed-controls">
  <button type="button" class="playback-rate-button mejs-active" data-value="1" title="Playback Speed 2x" aria-label="Playback Speed 1x">1x</button>
  <button type="button" class="playback-rate-button" data-value="2" title="Playback Speed 2x" aria-label="Playback Speed 2x">2x</button>
</div>
<hr>

This then allows page-level controls which update all the mediaelement-js players also.

Future commits may refine this, but right now it's a pretty small edit which has helped me test a thing.

IE11 fix - avoid JS template literals

Choose a tag to compare

@Lewiscowles1986 Lewiscowles1986 released this 09 Nov 18:13

IE11 compatibility release

Finally got to test in IE11

  • JS template literals are not supported. Simply store another var and then use very OG/OB getElementById

IE11 does have a race. This is likely because of the duct-tape approach this plugin takes to modularity