Hey folks!

I’ve been steadily working through the roadmap for lemmy-ui-next (which is a new alternative Lemmy frontend), and it’s getting to a point where I think https://next.lemm.ee is becoming quite usable. I’ve been personally using it as my main Lemmy frontend for several weeks now, and I know there are a few other brave users doing the same, so at this point, I’m confident enough to ask the wider lemm.ee population to try it out and share some honest feedback.

If you’re at all interested in this project, I would massively appreciate it if you could spend some time using https://next.lemm.ee and letting me know how you feel about it. I’m interested to hear about things like:

  • are you running into any issues or bugs
  • are there any things that generally annoy you
  • are you missing any features
  • what would it take for lemmy-ui-next to become your preferred frontend
  • anything else that comes to mind

Please keep in mind that this is still a work in progress - some features are planned but not implemented yet (see the roadmap linked above for more details), other features are half-finished and may be a bit buggy still!

Any feedback would really help me out, so please don’t hesitate to share!

  • TWeaKEnglish
    2·
    7 months ago

    I added an issue to the extension’s github, the plot thickens: https://github.com/jscher2000/Save-webP-as-extension/issues/30

    Hmm, the extension tries to inject the script that generates the button bar, but it fails with this error (in the add-on debugging inspector console):

    Uncaught (in promise) Error: Missing host permission for the tab

    I have not seen this on other images displayed in Firefox’s stand-alone image viewer.

    On the regular dev tools network tab for the image, I see this that the image is served with this header:

    content-security-policy: script-src ‘none’; frame-src ‘none’; sandbox;

    That seems to block even the built-in Firefox Screenshot feature (which uses extension APIs).

    I wonder whether applying the site’s CSP restrictions to the stand-alone image viewer was intentional or is a new bug. Have you used the extension on this site in earlier versions of Firefox?

    Anyway, I’ll have to think about whether there is a workaround for this. (Many extensions manipulate CSP for content blocking, and I don’t want to interfere with or break those.) And if there isn’t, how to at least alert the user to the nature of the failure.