Fix queried elements in document selector query search

[ajaayc]

@bhattcodes I discovered your Chrome extension and tried it out myself. Unfortunately it seemed to break at this line in background.js:

 try {
            window.document.querySelector(".FbBiwc").click();
        } catch {
            console.log("ERROR");
        }

It looks like the Leave call button does not always have a class of "FbBiwc," and the class may have changed since you wrote this script and/or the class may change depending on region and/or how Chrome is configured. The querySelector function returns null and the ERROR message prints.

I made this adjustment to the querySelector function, replacing it with:

window.document.querySelector('[aria-label="Leave call"]').click();

I believe this change will be more robust because it instead relies on the label of the button, not the class. Hopefully the label will always be "Leave call."

[ajaayc]

My second commit c074815 makes a tweak to the feature of leaving the call when the number of attendees is lower than some threshold. The line

document.querySelector(".gV3Svc>span")

seemed to yield an error for me. I suspect that Google Meets has changed recently, causing the class id to be different. I replaced it with:

document.querySelector(".uGOf1d")

This fix assumes that the classID of that element won't change...this may or not be a valid assumption, but I looked through the div and there didn't seem to be a reliable way to get the number of attendees without relying on the classID--unlike the fix from the previous commit that looks at the button label.

[lordofthebrain]

Don't use:
window.document.querySelector('[aria-label="Leave call"]').click();
in other languages the aria-label has a different value.

Use this instead:
window.document.querySelector("button.QQrMi").click();

[ajaayc]

Thank you, @lordofthebrain. I did not know that aria-label has a different value depending on the language. I made the update and replaced the aria-label reference line to window.document.querySelector("button.QQrMi").click(). I also packed the end meeting procedures into a function called endCall() to eliminate duplicated code.

I verified that with my changes, all 3 features still work and that the Chrome extension is still functional when I load it locally into the browser following Step 2 of these instructions from Google Support.

[lordofthebrain]

Thank you, @lordofthebrain. I did not know that aria-label has a different value depending on the language. I made the update and replaced the aria-label reference line to window.document.querySelector("button.QQrMi").click(). I also packed the end meeting procedures into a function called endCall() to eliminate duplicated code.

I verified that with my changes, all 3 features still work and that the Chrome extension is still functional when I load it locally into the browser following Step 2 of these instructions from Google Support.

Good work! For me, the extension also works again as it should be.