FfChrome and NoScript

  1. jmbolivar

    Member

    { #1 — 3 years ago }

    NoScripts stops working properly when Ffchrome is installed. Ffchrome itself doesn't work smoothly either.

    Would be good to be able to white list apps we do not want Ffchrome to take into account...

    Thanks and keep up with the great work!

    JM
  2. Administrator

    Key Master

    { #2 — 3 years ago }

    FfChrome has been tested to work fine by itself. If you provide us screen-shots we would be able to say more about what is happening.

    NoScript is looking for certain separators which do not exist. Thus it fails to insert certain items.
  3. jmbolivar

    Member

    { #3 — 3 years ago }

    Thank you for the response.

    Sorry, but there is no screen-shot to show. When FfChrome is enabled NoScript just stops working.

    I can still see its icon on the status bar but it behaves crazy (i.e. info is not relevant to the page displayed) and the "Options" button that NoScript displays at the bottom right of the page has the page-related options missing (only shows the generic ones).

    It's a pitty but cannot afford not having NoScript operational so will have to disable FfChrome until this is solved on either side.

    JM
  4. jmbolivar

    Member

    { #4 — 3 years ago }

    Hi again,

    Just got this answer for the developer of NoScript:

    Thanks you for your report, I managed to reproduce the issue.
    Unluckily, this is not NoScript's fault at all: NoScript's menu is composed dynamically on the fly, and relies on some of its own element to be in the document in order to have reference insertion points. FfChrome, instead, hijacks and remove these NoScript's elements (in this specific case a menu separator item), therefore NoScript breaks because they're missing.
    I suspect NoScript is not the only extension broken by FfChrome's behavior: many other need to compose their menus on the fly (even if NoScript's is arguably one of the most complex), but this problem can only be fixed by FfChrome which should take a less destructive approach (e.g. hiding, rather than removing, menu items and separators).
    Please contact FfChrome's author for a fix.

    Hopefully you can find an alternative way to FfChrome to do its job without breaking other extensions.

    Thanks!

    JM
  5. Administrator

    Key Master

    { #5 — 3 years ago }

    FfChrome does not remove anything, just hides them.
  6. Administrator

    Key Master

    { #6 — 3 years ago }

    I gave it more thought and here is what I have to say.

    The alleged remarks by the other addon developer are quite inflammatory. While I haven't come across an extension which is 100% compatible with the other almost 10000 extensions available on AMO, with due respect to everyone, this is not a moment for finding faults with other's extensions. That said, extension developers aren't the best at providing support given that they are hobbyists and amateurs and find time to satiate their creative satisfaction. While technical reasons can be many, the last thing we expect is someone mediating between two extension authors.

    I could easily say that I'm able to reproduce the issue myself and that NoScript is looking for certain menuseparators, I expect it to be stable enough to pull out hidden items since they do exist and have not been removed.

    But again compatibility at the moment is not the priority. And given that in today's world javascript is the lifeline of webpages, disabling javascript may sound to be a safety measure, I only see this as advertising a software on baseless fears.

    In contrast, If there's a compatibility issue with an extension it would be good for us to know. But expecting a fix may not be the right thing to expect. I respect and appreciate everyone's contribution to the opensource community and I'll personally work with the NoScript author to fix compatibility issues as and when I'm able to afford time.
  7. jmbolivar

    Member

    { #7 — 3 years ago }

    Hi again,

    Don't get me wrong. I also use ColorfulTabs and CuteMenu2 and think the idea behind FfChrome is great.

    I never install any extension that is not from a renamed developer, that's why my - maybe naive - expectation is that they work well all together.

    It's not my intention at all to mediate between the two of you. My aim was just to shed some light on the issue. Your first answer was pointing to something wrong in NoScript and I tried to have it solved on that side. You know the rest of the story.

    On my side, would like this incompatibility to be fixed ever, therefore allowing me to enjoy using FfCrome again.

    Thanks for your time and great job.

    JM
  8. Administrator

    Key Master

    { #8 — 3 years ago }

    No issues. It might be as trivial as waiting for a new version.

Reply

You must log in to post.