Using OnClick With OnMouseOver



When you mouse out, you want the pause to hide and the speaker to show. Update the onmouseout code so that it does that.


Git It!!!


Welcome to programming.


I want to try this one now.

player.isPlaying = function () {
    return player.paused === false;
if  (player.isPlaying()) {
  document.querySelector('#playButton2 .speaker').style.display='none';
  document.querySelector('#playButton2 .pause').style.display='inline-block';


What do I do with this part?

var player = document.getElementById('player2');
if  (player.paused) {


The player needs to exist first before you can add isPlaying to it, so put the var statement before that isPlaying line.


Like this?

var player = document.getElementById('player2');
player.isPlaying = function () {
    return player.paused === false;
if  (player.isPlaying()) {
  document.querySelector('#playButton2 .speaker').style.display='none';
  document.querySelector('#playButton2 .pause').style.display='inline-block';


Got it....


What's the difference between using function, and false?


The difference is that the if statement is easier for you, the programmer, to read and understand without needing to study the condition too closely.

Compare this version of the code:

if  (player.paused === false) {

with this improved version of the code:

if  (player.isPlaying()) {

With the second code example, it is much easier to understand that you are interested in whether the player is playing.


I have a question, how come I was originally told to use addEventListener, and would that have worked the same way, and, or, maybe that doesn't belong in this type of code setup?


Instead of the onmouseover and onmouseout sections, addEventListener could have been used in the onclick code, where you give it a function that contains what was in each of those sections.


How come you chose to go with, onmouseover and onmouseout instead of that?

Any particular reason?


Yep. The onclick code happens every time you click on the button, so the second time you click on it, a second set of mouse events would have been added. Eventually you would have hundreds of mouse events being run whenever you click, increasing each time. That is bad.

If you want to use addEventListener though, you can use it at the end of the body, in a <script> block of code instead.


no thank you.


I have one last question. Do you think


should be at the bottom of the code, or at the top, where it currently is?


I prefer to order the attributes in terms of importance. The onmouse stuff doesn't do anything until after the button has been clicked, so moving them after the onclick code makes a lot of sense.


Got it, ok.

Thank you so much for taking your time to help me with this code, I appreciate it.


I just thought I'd see what this process might have been like when coded in a different way.

Here for example is a module to toggle the playing. Each function is small, and simple, and does an effective job.

import images from "./images.js";
import utils from "./utils.js";

var button;
var player;
var icons;

function isPlaying() {
    return player.paused === false;
function show(iconName) {
function toggle() {
    if (isPlaying()) {
    } else {;
function togglePlayingHandler() {
function init(playButton, audioPlayer) {
    button = playButton;
    player = audioPlayer;
    icons = images.getSVGIcons(button);

    player.volume = 1.0;

    button.addEventListener("click", togglePlayingHandler, false);
export default {

Adding the hover feature means adding an event listener or two to the init section:

    button.addEventListener("mouseover", showPauseHandler, false);
    button.addEventListener("mouseover", showSpeakerHandler, false);

and those event handlers are as simple as the following code:

function showPauseHandler() {
    if (isPlaying()) {
function showSpeakerHandler() {
    if (isPlaying()) {

That's all that it takes. When the code is well built, making such changes are easy and effortless, instead of being the slog that we went through here in the previous posts.


Wouldn't it be nice @asasass, if you could use easier to understand code the above, in Blogger?

Wouldn't that be preferable?