Skip to content

Should "list of available images" also cache broken image responses? #4480

@domenic

Description

@domenic

Porting from https://www.w3.org/Bugs/Public/show_bug.cgi?id=25798.

We need web platform tests, and potentially a spec change, to see how many fetches get made in the following scenario:

  • An image is fetched, but comes back broken (network error etc.)
  • After that fetch completes, another <img> for the same URL is inserted into the document

Do browsers try to fetch again? Or do they just immediately give back the broken image?

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs testsMoving the issue forward requires someone to write teststopic: img

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions