Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lemmy 0.18.0 does not work when Firefox or Chrome saves a web page when viewing a Post ("Page Not Found") #1587

Closed
4 tasks done
RocketDerp opened this issue Jun 25, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@RocketDerp
Copy link

Requirements

  • This is a bug report, and if not, please post to https://lemmy.ml/c/lemmy_support instead.
  • Please check to see if this issue already exists.
  • It's a single bug. Do not report multiple bugs in one issue.
  • It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.

Summary

Something about the way the page is dynamically generated for the web browser results in no ability to "save as..." the web page on a desktop computer using either Firefox or Chrome browser. You end up saving a file that has none of the post or comment content from Lemmy.

Saves are often more useful than screenshots...

Steps to Reproduce

  1. go to a lemmy post on lemmy.ml
  2. Try to save in Firefox
  3. Try to save in Chrome
  4. Open the saved page, the content is not there

Screenshot from 2023-06-25 06-58-52

Technical Details

I don't think the OS is relevant, these browsers are pretty consistent on desktop platforms, and both major browsers have the same problem.

Lemmy Instance Version

0.18.0

Lemmy Instance URL

https://lemmy.ml

@RocketDerp RocketDerp added the bug Something isn't working label Jun 25, 2023
@alectrocute
Copy link
Contributor

I don’t see this being a feature added any time soon. @dessalines Feel free to reopen if you disagree.

@alectrocute alectrocute closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2023
@RocketDerp

This comment was marked as abuse.

@alectrocute
Copy link
Contributor

alectrocute commented Jun 25, 2023

It's deliberately save-hostile?

It relies on JavaScript to build the frontend experience. It would take significant overhaul to make dynamic pages “Save as…”-friendly, eg. full SSR support.

There’s hundreds of bugs that are higher priority right now that don’t require significant work. If you feel inclined, you’re welcome to make a PR, I’m sure it would be well received. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants