4 ms·

Huh? To the best of my knowledge, to get a development extension working in FF: 1. Ctrl-shift-a to open add-ons page 2. Click the cog, and select "debug add-o

by cdrini 4y ago

Huh? To the best of my knowledge, to get a development extension working in FF: 1. Ctrl-shift-a to open add-ons page 2. Click the cog, and select "debug add-ons" 3. Click "load temporary add-on" 4. Select a file in your extension. 5. Done. This worked for me earlier this week.

deleted 4y ago
[deleted]
user982 4y ago
Key word from the grandparent post: "permanently" Key word from the parent post: "temporary"
- cdrini 4y ago
  Ah I reckon what you meant was "Oh this approach only temporarily installed the add-on, your parent post was asking about a way to permanently install an add-on." Took me a while to figure out what you meant. Ah missed that; yep, the add-on will remain installed until the browser is restarted. That is a little annoying!
jakear 4y ago
Hm. I tried this with an super simple extension[1] I had lying around and couldn't get any network requests to work. The error thrown in console was a generic "NetworkError", but the network tab shows no relevant entries at all. Not a great developer experience, especially compared to chromium. https://github.com/JacksonKearl/FeelingBlue/blob/main/extension/chromium/manifest.json https://github.com/JacksonKearl/FeelingBlue/blob/main/extens...
- cdrini 4y ago
  Odd! Were you trying to fetch a public, CORS-enabled API? That should just work. If you were trying to make a network request for a non-CORS endpoint (eg fetch the google homepage or something), you'll need to add the domain to your permissions section. Eg: "permission": [ "storage", "https://google.com https://google.com" ]
  - old_hat 4y ago
    Not OP, I built an extension for a site that sent CSP headers. Because the browser extension wasn't allowed in the list of JS sources, it all borked. Not certain that's this user's issue, but that is another thing to check.
    - jakear 4y ago
      I suspect this is it. There were a lot of things logged to console for twitter violating its own CSP, but I didn’t see any for my script. It seems the overall handling of network errors in add-ons has a lot of room for improvement. It should be noted that chromium allows the network request regardless of the CSP. This is the correct, User-Empowering approach. Firefox’s deference to the Origin to control the code the User is attempting to run is the antithesis of what a User Agent ought to be.
  - jakear 4y ago
    I have CORS configured to allow the https//twitter.com/ origin. I could see firefox perhaps using a different origin for worker scripts? But hard to tell since the network tab doesn’t show any of the requests. I could set up server logs locally, but there’s only so many hours in my life.

by cdrini 4y ago

deleted 4y ago

[deleted]

user982 4y ago

Key word from the grandparent post: "permanently" Key word from the parent post: "temporary"

cdrini 4y ago
Ah I reckon what you meant was "Oh this approach only temporarily installed the add-on, your parent post was asking about a way to permanently install an add-on." Took me a while to figure out what you meant. Ah missed that; yep, the add-on will remain installed until the browser is restarted. That is a little annoying!

jakear 4y ago

Hm. I tried this with an super simple extension[1] I had lying around and couldn't get any network requests to work. The error thrown in console was a generic "NetworkError", but the network tab shows no relevant entries at all. Not a great developer experience, especially compared to chromium. https://github.com/JacksonKearl/FeelingBlue/blob/main/extension/chromium/manifest.json https://github.com/JacksonKearl/FeelingBlue/blob/main/extens...

cdrini 4y ago
Odd! Were you trying to fetch a public, CORS-enabled API? That should just work. If you were trying to make a network request for a non-CORS endpoint (eg fetch the google homepage or something), you'll need to add the domain to your permissions section. Eg: "permission": [ "storage", "https://google.com https://google.com" ]
- old_hat 4y ago
  Not OP, I built an extension for a site that sent CSP headers. Because the browser extension wasn't allowed in the list of JS sources, it all borked. Not certain that's this user's issue, but that is another thing to check.
  - jakear 4y ago
    I suspect this is it. There were a lot of things logged to console for twitter violating its own CSP, but I didn’t see any for my script. It seems the overall handling of network errors in add-ons has a lot of room for improvement. It should be noted that chromium allows the network request regardless of the CSP. This is the correct, User-Empowering approach. Firefox’s deference to the Origin to control the code the User is attempting to run is the antithesis of what a User Agent ought to be.
- jakear 4y ago
  I have CORS configured to allow the https//twitter.com/ origin. I could see firefox perhaps using a different origin for worker scripts? But hard to tell since the network tab doesn’t show any of the requests. I could set up server logs locally, but there’s only so many hours in my life.