3 ms·

Both of these seem like uncommon edge cases. I can't remember the last time I actually "saved a webpage" - I think in my using the web for nearly the past 30 ye

Both of these seem like uncommon edge cases. I can't remember the last time I actually "saved a webpage" - I think in my using the web for nearly the past 30 years that functionality hardly ever worked well in the first place. I do use print-to-PDF fairly often, but honestly don't know how lazy load works in that scenario. If you choose to print all pages and it doesn't include lazy loaded images, I'd just consider that a bug.

forgotmypw17 3y ago
For you, they are uncommon edge cases. For me, they are everyday usage.
- yathaid 3y ago
  The problems lazy loading solves is an everyday issue for me. So ... I guess the lack of user control here is the annoying part. Hopefully in the next round of standards updates this makes it in.
  - hahn-kev 3y ago
    I mean it wouldn't be hard to run a simple user script to add or remove all lazy attributes, though this isn't a solution for everyone, but most people don't care either.
rightbyte 3y ago
Given how much link rot there is I would have wanted all my non-porn non-bank website visits to be saved to some encrypted folder, in some way. Especially since Google got so bad you can't refind webpages you know exist.
- Aerroon 3y ago
  I wish browsers did this automatically so that the back button works properly instead of being just a guess on whether you pressed it or not.
  - madphilosopher 3y ago
    I wish the back button would bring back the rendered view of a page from a cache so that it would be (a) instant, and (b) not make any network requests. It seemed to me that older versions of the Opera browser did this, and the text-based "links" browser seems to do this today.
    - periapt 3y ago
      I'm confused - my browser does exactly that, and so do others' around me. I've even had an issue on a project recently caused exactly by the rendered view being saved for the back button. I've also had to demonstrate a possible issue with full page loaders on a regular website twice for the same back button reason - because apparently people (or at least several of my colleagues) don't find browsers' native request loading indication enough anymore... Rotten by JS loaders and SPA's, I guess?

forgotmypw17 3y ago

For you, they are uncommon edge cases. For me, they are everyday usage.

yathaid 3y ago
The problems lazy loading solves is an everyday issue for me. So ... I guess the lack of user control here is the annoying part. Hopefully in the next round of standards updates this makes it in.
- hahn-kev 3y ago
  I mean it wouldn't be hard to run a simple user script to add or remove all lazy attributes, though this isn't a solution for everyone, but most people don't care either.

rightbyte 3y ago

Given how much link rot there is I would have wanted all my non-porn non-bank website visits to be saved to some encrypted folder, in some way. Especially since Google got so bad you can't refind webpages you know exist.

Aerroon 3y ago
I wish browsers did this automatically so that the back button works properly instead of being just a guess on whether you pressed it or not.
- madphilosopher 3y ago
  I wish the back button would bring back the rendered view of a page from a cache so that it would be (a) instant, and (b) not make any network requests. It seemed to me that older versions of the Opera browser did this, and the text-based "links" browser seems to do this today.
  - periapt 3y ago
    I'm confused - my browser does exactly that, and so do others' around me. I've even had an issue on a project recently caused exactly by the rendered view being saved for the back button. I've also had to demonstrate a possible issue with full page loaders on a regular website twice for the same back button reason - because apparently people (or at least several of my colleagues) don't find browsers' native request loading indication enough anymore... Rotten by JS loaders and SPA's, I guess?