Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

In-page extension icon won't display until after page refresh

  • 7 replies
  • 1 has this problem
  • 3 views
  • Last reply by bklounge

more options

Customers use our SaaS in conjunction with 3rd party apps such Basecamp, GitHub, JIRA, etc. Our in-page extension icon is usually displayed next to checkboxes (to-dos), issues and so forth. Clicking the icon launches an embedded panel with more content.

The in-page extension icon should always be visible. Only until recently, the icon is not visible after initial page load. Users must then manually refresh the page to see the icon. Please see the attached animated GIF for a visual reference of the issue. The visibility issue is limited to Firefox; Chrome and Safari work as expected.

Is this possibly related to a setting / preference configurable by end-users? Any insight or places to point us to are appreciated!

Customers use our SaaS in conjunction with 3rd party apps such Basecamp, GitHub, JIRA, etc. Our in-page extension icon is usually displayed next to checkboxes (to-dos), issues and so forth. Clicking the icon launches an embedded panel with more content. The in-page extension icon should always be visible. Only until recently, the icon is not visible after initial page load. Users must then manually refresh the page to see the icon. Please see the attached animated GIF for a visual reference of the issue. The visibility issue is limited to Firefox; Chrome and Safari work as expected. Is this possibly related to a setting / preference configurable by end-users? Any insight or places to point us to are appreciated!
Attached screenshots

Modified by bklounge

Chosen solution

bklounge said

For the benefit of other forum users, the web doc from above states that "Firefox 57 drops support for legacy add-on types, including legacy add-ons that embed WebExtensions."

Hi bklounge, since the extension works on a reload, I don't think it's a Legacy extension.

It looks like the icons are there for a split second but then they clear for some reason. ??

There is a forum for help with add-on development where they might recognize the issue:

https://discourse.mozilla.org/c/add-ons/development

Read this answer in context 👍 1

All Replies (7)

more options

Hello bklounge, thanks for inquiring -- I'll escalate this to a moderator or employee ASAP.

more options

Hi Mkll, thanks for the fast reply! After posting my question I noticed I was not using the most recent FF version. I installed 57.1 and the issue still occurs.

more options

If you're an extension developer SUMO isn't really the place for you to get help -- Please see the developer documentation here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions

more options

Thanks for the heads-up. I'm the product manager, not the developer. Looking at the dev documentation, I'm guessing this developer web doc is relevant. Will have developer take a look.

For the benefit of other forum users, the web doc from above states that "Firefox 57 drops support for legacy add-on types, including legacy add-ons that embed WebExtensions."

more options

That is correct and the info was public and put out to developers over a year ago to rewrite their code. To be ready by version 57.

Sorta strange. But ya, you're in the wrong place and maybe a year behind. g'luck

more options

Chosen Solution

bklounge said

For the benefit of other forum users, the web doc from above states that "Firefox 57 drops support for legacy add-on types, including legacy add-ons that embed WebExtensions."

Hi bklounge, since the extension works on a reload, I don't think it's a Legacy extension.

It looks like the icons are there for a split second but then they clear for some reason. ??

There is a forum for help with add-on development where they might recognize the issue:

https://discourse.mozilla.org/c/add-ons/development

more options

Hi jscher2000, thanks for the link to that forum. Will pass it along to our developer who, BTW, confirmed it's not a legacy extension. That the issue coincided with the release of 57.0 certainly makes it interesting!

Appreciate everyone taking the time to reply!