We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
lazy
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:
Current esl-image behavior based on the separate lazy-triggered attribute
esl-image
lazy-triggered
Request to change esl-image lazy processing to the following flow:
lazy='manual'
triggerLoad()
lazy='auto'
The text was updated successfully, but these errors were encountered:
Wouldn't implemented due to drop of support of esl-image
Sorry, something went wrong.
Natalie-Smirnova
No branches or pull requests
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:
lazy
attribute = no block for loadinglazy
attribute -> blocking load process, IO observation success leads to removal oflazy
attributeCurrent
esl-image
behavior based on the separatelazy-triggered
attributeRequest to change
esl-image
lazy processing to the following flow:lazy
attribute = no loading blocklazy='manual'
= blocks image loading until thelazy
attribute is removed (manually by DOM mutation or by the call oftriggerLoad()
method)lazy='auto'
(orlazy
w/o value) = blocks image loading until thelazy
attribute is automatically removed by IOThe text was updated successfully, but these errors were encountered: