WebCrypto in Chromium is primarily implemented atop of BoringSSL. For any specific algorithm, one would have to chase the function calls to confirm, however.
Note that BoringSSL in Chromium is not built in FIPS mode and, of the platforms that Chromium supports, only Android has seen a BoringCrypto validation. (A list of which can be found
here.)
Also, the security policy of the module may require specific functions to be called to enforce FIPS requirements and Chromium may not be calling those versions of the functions.
Cheers
AGL