Closed Bug 1131771 Opened 10 years ago Closed 5 years ago

If dom.storage.enabled = false the site support.mozilla.org does not show pictures.

Categories

(support.mozilla.org :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: iceberg, Unassigned)

References

Details

(Whiteboard: p=2 u=user c=kb s=)

Steps to reproduce: Set in about:config dom.storage.enabled = false Open any page of the support site support.mozilla.org If the page contains images these are not displayed. Actual results: The images are not shown. Expected results: Images must be shown.
See Also: → 1017850
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Firefox → support.mozilla.org
Version: 35 Branch → unspecified
See Also: → 1132204
Not see images causes a problem. Whilst it may be that the site can get better by activating the dom storage (or cookies), because the disable all images otherwise? Free nastiness. Compounded by the fact that it is a support site, must do everything to be seen, whatever the Firefox settings. Do not show images as default, if Firefox settings are not "pleasing", is conceptually wrong.
Flags: needinfo?(mcooper)
Personally, I think that disabling this feature is not something we should support. In particular, the only way to change it is via about:config. Before entering about:config a warning is given "This might void your warranty! Changing these advanced settings can be harmful to the stability, security, and performance of this application. You should only continue if you are sure of what you are doing. [I'll be careful, I promise!] " I don't think we should be supporting changing these settings. If someone were to change "security.tls.version.max" in a way that broke SUMO, we would not support that user. They have opted in to a broken experience. All that being said, localStorage is automatically disabled in private browsing mode, and I think that private browsing mode is something we *should& support. Because of this, I recommend we switch our localStorage use to the library localForage[0], which will safely deal with this instead of us constantly chasing around errors. It will be more work in the short term, but it will decrease developer work in the future. [0]: https://github.com/mozilla/localforage
Flags: needinfo?(mcooper)
Whiteboard: p=2 u=user c=kb s=2015.4
I can't comment on anything else, but private mode still shows pictures, we should take that into account when we prioritize.
Whiteboard: p=2 u=user c=kb s=2015.4 → p=2 u=user c=kb s=
See Also: → 1141065
I cannot reproduce this now. Is it enough to change the "dom.storage.enabled" to "false", or are there any extra steps needed?
Priority: -- → P5
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.