As of Firefox version 44 (currently in beta) Components is no longer available, causing the bootstrap code to assign a value to unsafeWindow (which is not possible). I'm currently checking some of the scripts in the forum to make sure they won't break once Firefox 44 goes live (January 26). I've checked your userscript and it uses unsafeWindow extensively, but you should be fine by just removing the bit of code below. That code won't do anything useful any more as this way of retrieving the unsafeWindow has been removed. I've seen other scripts just using unsafeWindow without that check and they seem to run fine.

Hey, please be aware your script still seems to rely on the Waze object, which will be removed in one of the upcoming beta releases. You can test this yourself in the beta environment as the proxy object implemented by Waze (to make window.Waze point to window.W) also logs an error in the web console now.

Running into a problem. Running the script via Tampermonkey in Chrome.

I can no longer save any changes I make to the settings menu, and clicking save will apply the changes, but will not close the settings window. Once I reload the editor, all my changes are lost.

I've disabled every other extension except tamper monkey, and I'm only running this script in Tamper Monkey. I cleared my cache, deleted all cookies, and restarted Chrome. Same problem.

Any idea how to troubleshoot?
EDIT: It looks like my work is blocking the URL used by Responsive Text. Would that cause the save button to fail?

Update - I can confirm it is something with my work's URL filter blocking the script from working. I took the computer home and it works fine. So not sure if it is just the Responsive Text .js that is causing the problem, or there's some other .js or external reference.

Great update. I was wondering about the following:

You can replace a block by a google spreadsheet key.
Here is a sample spreadsheet. You can edit it, and fork it for your own purpose:
... edit#gid=0
Lines beginning with 'UserName' are ignored to keep an understandable header.
As you can see in the URL, the key is:
1G9-TweVLOeP023OTWZsKxkv5JDgXtVV1BJ-fKNUkF0c

Is their anyway we can get some sort of text formatting? For example say I enter the room can the custom message be defined to display in Red or White (text) on Red(backgorund) or Bold?

So long, and thanks for all the fish.

Whilst reviewing the code for this script to resolve a conflict with WME Fix UI (the conflict was my fault, by the way!), I spotted a couple of errors.

In 3 places in the script, the attribute length is mis-typed as lentgh. I didn't investigate to see exactly what the script was doing at these points, but it doesn't seem to be breaking anything critical.

Caart wrote:Hello.

Without Fix UI, the Bell/Zzz icon is melted with the Profile icon, which causes impossibility to click the Profile button.
However (with Fix UI), this is really a useful function, thanks laurenthembprd for idea and JustinS83 for coding.

Caart

I'm guessing Justin added the User Profile feature whilst using WME FixUI - which makes extensive changes to the Chat window - hence the problem!

@Justin - if you want to make your addition work without FixUI, then I'll make necessary changes to accommodate it's addition.

I think a great new addition would be a little colored circle next to each persons name in the chat room, which would display if they are active.

Green ball would be 'Active'
Yellow ball with a clock would mean Inactive for last 5(?) mins (not typing/moving mouse).
Yellow ball would mean short term AFK
Red ball is for a long term AFK.
Red ball with a clock would mean Inactive for last 30(?) mins (not typing/moving mouse).
Perhaps a grey ball for a Do Not Disturb?

People can select if they want to be either green/yellow/red/grey, only the clock ones arnt set by the user.

This would allow users to easily see if a person is online. As a noob to WME, I ask for tips and guidance a lot, and this would be more effective than going down the list saying "@User hello. @User you there? @User can you help me out for a sec?" etc. and just ask a person who is green.

dummyd2 wrote:Hi Janek,

for sounds, I use the Javascript object "Audio" that loads an URL from google.
Here is an old post: http://stackoverflow.com/questions/1323 ... d-browsers
Perhaps, the problem is still alive with https

Also:
https://github.com/processing/p5.js/issues/465
seems to need a user action to play a sound.

Sorry, but I can't debug it or look for a workaround.

No idea if howler.js would help, but hope that it will help you in your troubleshooting