Open Bug 1622090 Opened 2 years ago Updated 4 months ago

Implement lazy-load for iframe

Categories

(Core :: DOM: Core & HTML, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: hiro, Unassigned)

References

Details

(Keywords: dev-doc-needed, Whiteboard: [layout:backlog][parity-chrome][parity-edge] )

No description provided.

Do we need a tracking bug for this when there's no specification yet?

Is there even a new specification issue regarding iframes (and other elements loading remote resources)? It looks like the outcome of https://github.com/whatwg/html/issues/2806 was only lazy loading for <img> elements, in the end.

(In reply to Anne (:annevk) from comment #1)

Do we need a tracking bug for this when there's no specification yet?

I assume, lazy loading for iframes will eventually also be specified. So either this bug should be kept open or closed for now and be reopened once specified in order to implement it.

Sebastian

Whiteboard: [layout:backlog]

Now that we triage by severity, setting this bug's priority to P2 to represent near-term backlog status. See https://wiki.mozilla.org/Platform/Layout#Backlog_Tracking_in_Bugzilla

Priority: -- → P2
See Also: → 1483280
Whiteboard: [layout:backlog] → [layout:backlog][parity-chrome][parity-edge]
You need to log in before you can comment on or make changes to this bug.