diff --git a/controls.md b/controls.md index 088bee8a..63b17fa3 100644 --- a/controls.md +++ b/controls.md @@ -2,9 +2,9 @@ This is the markup that is rendered for the Plyr controls. You can use the default controls or provide a customized version of markup based on your needs. You can pass the following to the `controls` option: -* `Array` of options (this builds the default controls based on your choices) -* `String` containing the desired HTML -* `Function` that will be executed and should return one of the above +- `Array` of options (this builds the default controls based on your choices) +- `String` containing the desired HTML +- `Function` that will be executed and should return one of the above ## Using default controls @@ -81,14 +81,14 @@ The classes and data attributes used in your template should match the `selector You need to add several placeholders to your HTML template that are replaced when rendering: -* `{id}` - the dynamically generated ID for the player (for form controls) -* `{seektime}` - the seek time specified in options for fast forward and rewind -* `{title}` - the title of your media, if specified +- `{id}` - the dynamically generated ID for the player (for form controls) +- `{seektime}` - the seek time specified in options for fast forward and rewind +- `{title}` - the title of your media, if specified ### Limitations -* Currently the settings menus are not supported with custom controls HTML -* AirPlay and PiP buttons can be added but you will have to manage feature detection +- Currently the settings menus are not supported with custom controls HTML +- AirPlay and PiP buttons can be added but you will have to manage feature detection ### Example @@ -131,13 +131,13 @@ const controls = `
- -