Skip to content

Specify bfcache behavior with proper tests #81

@saschanaz

Description

@saschanaz

I intend to add a bfcache test where any active lock/request prevents caching, matching the current Chrome Dev 96 behavior.

Is this something you want to change or are you okay with the current Chrome behavior? To me it sounds reasonable enough, and in that case I think we should at least add a note about it, if it's not something can be specced.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions