Skip to content

What are known browser_validations quirks? #367

@kevinh-csalabs

Description

@kevinh-csalabs

The option config.browser_validations is set to false by default and 'recommended due to some quirks from different browsers.'

Is there any documentation on what browsers or what quirks to be on the lookout for that were identified as a reason to choose keeping this option as a default? I'm not looking for an exhaustive list, but any direction on the issues to look out for would be appreciated as I couldn't turn up anything in a google search or past issues.

It looks like this was originally true but changes back just shy of a decade ago related to error styling: ffac64e
and documentation was updated in 2014: cbeeb3b#diff-523378c56f55355a780b4524e2ee91f1b93de9a7fc9ae8395739e805eb187089R202

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