CSP - Why Firebug (with Waterfox) don't work well on Mozilla Addons Pages (AMO New Design) ?

decembredecembre
edited July 2019 in Style Development Waterfox
When i want inspect an element of their new design, the hover in the HTML tab of Firebug don't show the highlight area in the page.

And with the Official Firefox it's worth:
the HTML tab is empty...

What's the problem with these pages ?????

EDIT:
I tested (with success) the solution provided by Jeferson
in :
There is a bug (#1326146) where sites with/without certain Content-Security-Policy (CSP) headers block the Rules pane of the Inspector.
As a workaround, you can turn off CSP, at the risk of some alien content running in pages. In about:config, toggle security.csp.enable to false

So i passed:
security.csp.enable
security.csp.enableStrictDynamic
security.csp.experimentalEnabled;

to false and now firebug work as i do.

Now the question is :
Their is a way to toggle quickly these about:config settings ?.


Ps:
I don't like the new design (Firefox continue to break all we loved in it):
The soluce below is Not possible now !
But GOOD new : we can return to the old design (and use always my userstyle Mozilla Addon Widescreen:

In fact the New Design is for mobile and when you open the AMO it is enable by default.
If you want the OLD design it is her but you need to find the good link to enable it....
..../....
En fait, il est possible de repasser la version pour ordinateur, en cliquant sur "Afficher la version pour ordinateur" ou "View classic desktop site" en bas de la page (at the end of the page).
Mais ce n'est pas gardé dans les préférences de site, donc à refaire à chaque connexions, si cookies supprimés.

.../...

Comments

  • decembredecembre
    edited August 2018 Firefox
    Always with Waterfox 56.2.2, firebug need this tweak on about:config to work better on NEW design AMO pages.
    Any new about that ?

    I have too many problems on other sites with Firebug which can hang Waterfox with error messages about css.lib / or html.lib:
    How resolve that (i don't like the dev toolbar).

    Someone can fix this bug (yes i know Firebug support is discontinued, but ...) ?
  • JeffersonJefferson
    Firefox
    Is there a Firebug Holdouts forum? I'm sure you are not the only one, but I don't know the odds that there are others here.
  • decembredecembre
    Firefox
    Maybe someone on Waterfox project ....
  • anagrammaranagrammar
    Chrome
    image
  • decembredecembre
    [?]

    i retun on this problem for a new profile.
    If i only toogle:
    security.csp.enable to falsle
    i can use firebug on AMO site (to highlight the selection concerned by a selector on hover).

  • decembredecembre
    edited February 2020 [?]

    A summarize of my Firebug Stories :

    So like for many things with Firefox now, we need some work to regain these functions.
    You can too use Waterfox Classic.

    It Use Firefox 56 as a platform (inline integration of the latest Firefox ESR security patch) and supports LegacyAddons.

    But we need some work to regain these functions.

    Primary, install Firebug.
    Firebug isn't being developed or maintained any longer because it can't work with e10s. Go to about:preferences#general: set e10s Multi-process to false
    NOTE: The Multi-process architecture improves the browser's stability, performance and security by separating tasks into processes, you disabling it at own responsibility.

    To make Firebug active, you need some tweaks in the about:config.
    Without these about:config tweaks, when you click on the firebug icon, a message say "you can't use it" and the Devtools open instead Firebug.

    So, Open about:config to set these values:

    • privacy.resistFingerprinting.block_mozAddonManager (empty and set
      it to "true")
    • privacy.resistFingerprinting (empty and set it to "false")
    • extensions.webextensions.restrictedDomains (let it empty)

    Read:
    Firebug is not working with Firefox version 50.0

    And maybe if you wants work on pages protected (like AMO pages), you need add these tweaks too:
    - security.csp.enable
    - security.csp.enableStrictDynamic
    - security.csp.experimentalEnabled

    Pass them to "false".

    And normally that's good now ( i hope don't have forgotten something)...

    Read:
    CSP - Why Firebug (with Waterfox) don't work well on Mozilla Addons Pages (AMO New Design) ?

    PS, Why use outdated Firebug?
    Yes, some useful functions are pushed in the New DevTools.
    But sorry, Firebug (with the help of FirePath) is better and simple for CSS.
    I tested Quantum and DevTool:
    for Css it's a pain.

    With Firebug:
    - No need shortcut.
    - Work on page and on another without reload the DevTolls for the it.
    - Search in is clear and comfortable.
    - Hover a selector modified by an userstyles provide a readable info
    about it in the HTML view.
    Read:

Sign In or Register to comment.