We encrypted that as “Bugfix layers visibility” 
But it’s good that you pointed it out more clearly. 
It’s always so nice when all the broken things stop being broken, feels good.
Thank you!
Using Chrome 81.0.4044.138 on a Mac. Upgraded to TB 1.8.20 and only running TB - no other extensions. The dropdown menu shows up until all the top of screen messages e.g. “WME Toolbox: No private messages…” ending with “WME Toolbox: Country changed to United States” finishes scrolling, then the dropdown menu toolbox in the menu bar disappears. When the toolbox disappears, the following appears in the Console.
Still not working for me as well. Same Chrome version, Mac, verified Toolbox was updated to 1.8.20, both in WME and in the Chrome Web Store.
It worked for me for a little while (hence earlier thank you post), but once again not working. Verified on current version.
The issues I was having with the HN layer getting stuck on, and PIE losing its settings, both requiring a tab refresh to fix, had also cleared up (related?), but now they are both happening again frequently as well.
Sorry! I know it’s frustrating!
Greetings wazers, new version toolbox does not solve the chrome activation of this valuable tool, help
Issue reproduced and fixed in the next release
I am using the latest version.
The settings menu icon has disappeared. It’s visible during loading, but then suddenly it’s gone. I tried also with all other scripts disabled, but same outcome.
I also tried to switch the extension off and on again, and also in an incognito browser window. All to no avail.
I’m using Chrome (Version 81.0.4044.138 (Official Build) (64-bit)) on a W10 machine
I have been told that this has nothing to do with Toolbox, something in Waze is messing with the items added to the top bar.
I have had long running issues with the editor getting stuck in between HN mode and normal mode, displaying elements of both and quickly breaking down. Even a single HN edit was causing the error, making a tab refresh necessary. Was pulling my hair out trying to figure out which scripts were doing it in Tampermonkey, just spaced that WMETB might be the culprit since it is not in TM.
Sure enough, turns out this issue only occurs with WMETB running, even with all other scripts off, and is reproducible 100% of the time. Please let me know what info - if any - is needed to help fix. I really depend on WMETB because it’s fantastic, but right now it’s making editing a real chore with having to reload the browser constantly.
If it helps troubleshoot, also be advised that, from a fresh browser reload, if you invoke HN mode and cause this error, the custom place categories set in the dropdown defined by the PIE script also break at the same time.
Note that the “stuck HN mode” problem exists whether or not PIE (or any other script) is running, but I thought that knowing the error was also affecting PIE like this might help.
And… more info. While editing I noticed that some of my keyboard shortcuts stopped working. Some custom ones and some default ones stopped (examples: CTRL+A to select all roads failed, “1” to clear road geometry failed), yet other custom and default ones were unaffected (examples: CTRL+C to copy text worked, “V” to clean up revcons worked). I could still manually select all segments with the panel button, and I could still clear geometry one node at a time with “D”. Strangely inconsistent behavior. However, during this time, I was able to repeatedly edit HNs without the HN mode stuck problem happening at all, and other than some shortcuts not working as described, WMETB continued to function fine as far as I could tell.
Suspicious the two were related, I functioned as long as I could with some of the failed keyboard shortcuts, made it about an hour. Finally had something else go wrong to force the tab refresh, and now we’re back to breaking it with every HN edit. 
WME toolbox does not work in the latest Beta version on firefox 76.0.1
ReferenceError: OL is not defined WME_Toolbox.beta.min.js:885:80
<anonyme> moz-extension://6070a55c-a415-40db-b109-0f992d9fa2be/scripts/WME_Toolbox.beta.min.js:885
<anonyme> moz-extension://6070a55c-a415-40db-b109-0f992d9fa2be/scripts/WME_Toolbox.beta.min.js:1014
Some things I’ve been able to figure out with Toolbox. This is all consistent with other scripts running or disabled.
Nearly 100% of the time loading WME causes the Toolbox menu to disappear. When the Toolbox menu is not there, Toolbox does not do any highlighting (no soft turns, u-turns, loops, TIOs, etc.). Additionally, HN mode sticks when leaving HN mode. The Toolbox functions in the floating toolbar continue to work.
I have also found that if I have Chrome’s DevTools open when loading WME (and getting breakpoints with every uncaught exception) everything in Toolbox works correctly. HN mode doesn’t stick.
Having DevTools open when loading WME works 100% of the time to get Toolbox to function correctly.
Have discovered, after working with it for some time now thanks to the above tip, that having Developer Tools open does seem to reduce the frequency of WMETB having issues, but it is not a 100% solution. While the toolbox icon tends to always stay on now, I am still frequently getting stuck in partial HN mode even with the DT panel open. Have also noted that having DT open tends to cause issues with other scripts sometimes not loading or running properly (specifically, WMEPH, PIE, GIS-L).
Same to me. Firefox 76.0.1 @ W10 (lastest updates)
A view weeks ago it was possible while reload the browser a view times. Today I don’t get it. Scrips ON/OFF doesn’t matter
Same thing happens with me. I’m running the latest Chrome and have been having trouble with Toolbox. I thought it was just a glitch where the icon on the top ribbon appeared briefly while loading WME page. But as soon as the loading completes, the small icon disappears. And today, it has become even worse. Toolbox isn’t loading at all, no matter how many times I’ve tried to refresh and reload WME.
A new WME Production was released today which broke TB. Be patient while they work on getting it fixed again.
The missing icon problem (and other issues) has been an ongoing concern for many for quite some time even before this WME release… hang in there for a fix, one is hopefully coming when time permits. 