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

[🚀esl-image]: simplify lazy handling #1649

Closed
ala-n opened this issue May 9, 2023 · 1 comment
Closed

[🚀esl-image]: simplify lazy handling #1649

ala-n opened this issue May 9, 2023 · 1 comment
Assignees
Labels
wontfix This will not be worked on

Comments

@ala-n
Copy link
Collaborator

ala-n commented May 9, 2023

As an ESL architect/user, I want consistent handling for lazy loading across components.

In bounds of #1641, a different approach for handling lazy processes was introduced:

  • no lazy attribute = no block for loading
  • lazy attribute -> blocking load process, IO observation success leads to removal of lazy attribute

Current esl-image behavior based on the separate lazy-triggered attribute

Request to change esl-image lazy processing to the following flow:

  • no lazy attribute = no loading block
  • lazy='manual' = blocks image loading until the lazy attribute is removed (manually by DOM mutation or by the call of triggerLoad() method)
  • lazy='auto' (or lazy w/o value) = blocks image loading until the lazy attribute is automatically removed by IO
@ala-n ala-n added the waits triage Issue that waits to be reviewed and handled label May 9, 2023
@ala-n ala-n added this to the ⚡ESL: 5.0.0 Major release milestone May 9, 2023
@ala-n ala-n removed this from the ⚡ESL: 5.0.0 Major release milestone Jan 17, 2025
@ala-n
Copy link
Collaborator Author

ala-n commented Jan 17, 2025

Wouldn't implemented due to drop of support of esl-image

@ala-n ala-n closed this as completed Jan 17, 2025
@ala-n ala-n added wontfix This will not be worked on and removed waits triage Issue that waits to be reviewed and handled labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants