| Does anyone happen to know where in the Chromium code base the implementation is hiding? The android version seems to use a library that's part of Google Play Services: /**
* Implementation of mojo BarcodeDetection, using Google Play Services vision package.
*/
and // The vision library will be downloaded the first time the API is used
// on the device; this happens "fast", but it might have not completed,
// bail in this case. Also, the API was disabled between and v.9.0 and
// v.9.2, see https://developers.google.com/android/guides/releases.
From: https://github.com/chromium/chromium/blob/c4d3c31083a2e14812...The desktop version references a third party library called "barhopper" here: https://github.com/chromium/chromium/blob/e1e495b29e1178a451... and barhopper seems to come from a non-public Google repo: 'src/third_party/barhopper': {
'url': 'https://chrome-internal.googlesource.com/chrome/deps/barhopper.git' + '@' + 'ad3c4382875afdd0340f1549f8b9c93cbbc16e37',
'condition': 'checkout_src_internal and checkout_chromeos',
},
from https://source.chromium.org/chromium/chromium/src/+/master:D...I didn't realize that Chromium had missing APIs compared to Chrome but maybe that's always been the case? This appears not to be a W3C standard: https://wicg.github.io/shape-detection-api/ I was interested in this because there are no really good open source DataMatrix decoders (to my knowledge) with the one in ZXing being basically unusable (last I checked) and libdtmx being ok but not comparable to commercial offerings. |
This feature uses native libraries and only works on Chrome OS, Android, and MacOS currently according to this page:
https://chromestatus.com/feature/4757990523535360