Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Issues related to some settings in about:config (RLBox, shadow-stack protection)

  • Aucune réponse
  • 0 a ce problème
more options

I have two questions:

1. Will WASM and JIT be turned on or not affect the operation of RLBox?

I currently have the following about:config settings set to false, I'm wondering if this will cause the RLBox to not function?

javascript.options.ion javascript.options.baselinejit javascript.options.native_regexp javascript.options.asmjs javascript.options.wasm

I hope Mozilla staff will consider listing the operating status of RLBox in about:support, so that it will be clear at a glance.

2. Enabling "security.sandbox.content.shadow-stack.enabled" will cause add-ons to not function properly.

This setting seems to have been around for a long time. Is there any progress on this? Chrome has supported this feature for quite some time.

I would be grateful if you could help clarify this and inform me of the answer.

I have two questions: 1. Will WASM and JIT be turned on or not affect the operation of RLBox? I currently have the following about:config settings set to false, I'm wondering if this will cause the RLBox to not function? javascript.options.ion javascript.options.baselinejit javascript.options.native_regexp javascript.options.asmjs javascript.options.wasm I hope Mozilla staff will consider listing the operating status of RLBox in about:support, so that it will be clear at a glance. 2. Enabling "security.sandbox.content.shadow-stack.enabled" will cause add-ons to not function properly. This setting seems to have been around for a long time. Is there any progress on this? Chrome has supported this feature for quite some time. I would be grateful if you could help clarify this and inform me of the answer.

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.