Mirrored at 7484c36.

Please check your JSHint messages in the left gutter of the Source Code tab next to the line numbers. In this case some of them are quite accurate. Thanks. :)

Re: @cuzi:

Cookie Controller enabled, which blocks cookies and DOM storage.

Yup that is partially it. Thanks for that... save me some time next week. :)

, which blocks cookies and DOM storage.

When disabled my Firefox (Fx) takes over since that Add-on uses the existing about: prefs e.g. the settings persist.

as this addon is not really popular.

There's also about:data in SeaMonkey (SM) so it's quite common for some browsers, especially Moz, to have these settings enhanced. Fx is about:permissions.

Re: @jgjake2:

Anything in particular you want included?

So there's one thing... fallback to DOM storage e.g try using the GM_* API first and if all else fails perhaps let the user know gently... perhaps with console.warn statement or better. This is how one of our earlier projects works.

Re: @jgjake2:

What kind of add-ons do you have?

Lots... will have to narrow it down to which ones as well as about:config changes. Like I said earlier I don't have enough time just yet to do the Add-on walk-about testing. Perhaps sometime next week will work for me.

What pops up in your console?

unsafeWindow and localStorage is what I recall from earlier... again depends on what active Add-ons I had. NoScript is the usual culprit for enforcing certain security restrictions but Moz is taking on that challenge as well. Will take some time to iron out the details for you... but not until at least next week.

Anything in particular you want included?

Don't know yet... testing stopped once the Add-on incompatibility was discovered. I'll try to redo my profile in case migration is a factor in the results... that takes a bit to do.

Seems to be working

Testing out #562

Re: @0097gvk:

Btw thanks for the extremely subtle hint... should be fixered now. :)

Re: @jgjake2:

... and this seemed like the place to get some feedback on it.

Impressive library and appears that you have spent a good deal of time developing this.

Off the top of my head a few things come to mind:

• Incompatibility with some Add-ons. Unfortunately your demo page only comes up on a clean browser profile. I disabled the usual suspects with security related Add-ons and it still didn't come up... at this time I don't have a spare moment to go debugging with you and other Add-ons
• Few things related to security in current Firefox release show up in the Browser Console... be careful as Moz and possibly GM may be changing unsafeWindow a bit.
• Nice combination specific to inclusion of some node projects and a few mashups from USO/OUJS.
• Care to consider sharing this in the Libraries section too with a webhook on your GH repo for greater exposure? ... Please ensure that you follow the Terms of Service though with a // @exclude * in your UserScript metadata block... otherwise it will get removed by moderation.

Thanks for sharing and it looks promising. :)

Re: @vitae:

Sorry, I guess the "enter image description here" part of posting an image doesn't do a damned thing.

Sample source

Invoked via the image toolbar icon in the comment reply:

![enter image description here](https://openuserjs.org/images/favicon16.png "enter image title here")

Example

See where it says "enter image title here"? That is where you should place what you want mouse hovers to show and is equivalent to the title attribute. You appear to have done this already. The "enter image description here" is equivalent to the alt attribute when images are not shown and some see (or hear for screen readers) your text instead. Some users have different browser configurations. e.g. does do something. Thanks.

Re: @goldstern:

... ob schon jemand eine Lösung

Vielleicht (perhaps) greasemonkey/greasemonkey#2033

Re: @trespassersW:

There are some slight differences in between the dev environment and pro running... so ensuring that production works. Sorry for the noise. I try to keep it at a minimum here.

Do you really want others to use your internal MAC address? I suggest you relook at not using the query string parameters on your redirect.

Translation courtesy of Microsoft Translator:

Bocor informasi pribadi Anda

Apakah Anda benar-benar ingin orang lain untuk menggunakan alamat MAC internal? Saya sarankan Anda relook tidak menggunakan parameter string kueri pada redirect Anda.

This doesn't appear to be JavaScript nor a UserScript.

You appear to have uploaded just a UserScripts metadata block... are you going to post some code with that?

ANNOUNCEMENT

Some of you here should only be using the Flag button in the sidebar to notify if something is typically dangerous. Please do not abuse the Flag option or those persons may be subject to removal from the site. If there is an issue with this script not working please leave a comment so @BastianKanaan can evaluate if a fix is necessary. Flagging the script for a bug is not currently a means to let Moderators and above know why.

Thank you.

@BastianKanaan
I have cleared all your flags. It would appear that some users were using it as a favorite button.

Translation courtesy of Microsoft Translator (hopefully done well):

ANKÜNDIGUNG

Einige von euch hier sollten nur verwenden der Schaltfläche "Flagge" in der Seitenleiste zu benachrichtigen, wenn etwas in der Regel gefährlich ist. Bitte missbrauche nicht die Flagge Option oder Personen, Entfernung von der Website unterliegen können. Wenn es ein Problem mit diesem Skript nicht funktioniert bitte einen Kommentar damit @BastianKanaan beurteilen kann, wenn ein Update erforderlich ist. Kennzeichnen das Skript für einen Bug derzeit kein Mittel, um die Moderatoren zu lassen und oben weiß warum.

Vielen Dank.

@BastianKanaan
Ich habe alle Ihre Flags gelöscht. Es scheint, dass einige Benutzer sie als bevorzugten Schaltfläche verwendet wurden.

Retest

Re: @decembre:

#233 and #359.

Re: @ParticleCore:

returning simply an empty <img> element.

That is intended behavior. RFEs of this nature should not be done in this discussion forum and ideally they should be done through the Development link as referenced in the footer. This forum is currently for UserScripts not the site itself. Thanks.

See also:

• https://github.com/OpenUserJs/OpenUserJS.org/pull/129#issuecomment-45699717

Re: @trespassersW:

what exactly did you mean?

See coulé.

Re: @decembre56gmail.com:

See this (First quotation response e.g. not yet)

Re: @jscher2000:

... try to avoid counting duplicates ...

Not sure if this is what you want from this but you may use @downloadURL in the UserScript metadata block and point it to https://openuserjs.org/src/scripts/jscher2000/Google_Hit_Hider_by_Domain_(Search_Filter_Block_Sites).user.js thus not counting updating installs on OUJS... provided the user.js engine supports it as well as no other Add-on interfering. I had to do a clean profile to determine that our serving wasn't at fault here and it's not GM's either... so one of my other bazillion add-ons calling on the server twice when it shouldn't. There is some indirect precedence for this and I have seen that with http/https as well. Hope some of this helps. :)

Re: @Ede_123:

You too! :) Thanks from all of us!

Interesting script here and documented okay.

If you don't use an IIFE FB will have a better chance at detecting this since it's in the global content scope.

All libraries with incomplete UserScript metadata blocks and not meeting the Terms of Service (TOS) requirement for libraries have been removed. Those users have had ~50 days to fix this. Future uploads that don't meet the basic library requirements may be subject to library removal and possibly account removal. So please abide by our TOS. Thanks.

Re: @Marti:

... soon after ...

"Soon after" is just around the corner. All libraries will be reevaluated tomorrowish. :)