Anyone in test for the domain able to attest that formal USB compliance verification would have detected the design defect that this hack resolves?

crote 20 hours ago | parent | next [-]

It absolutely would. This is an "didn't even read a 5-paragraph AI summary of the spec" level of a design defect.

If you need this fix, it will literally refuse to work with any spec-compliant USB-C device on the other side of a C-C cable. No way to miss it.

Wonder if there are USB C cable testers that detects this.

In practice, most if not all networking/hardware department carries a ethernet cable tester but somehow not true for USB cables.

	▲	Ajedi32 20 hours ago \| parent \| next [-]
		It's not the cable that's the problem here; it's the device you're plugging into the cable. You don't need a cable tester to detect this problem; just plug the device into a spec-compliant USB-C power brick with a USB-C cable and see if it fails to charge.
	▲	seba_dos1 20 hours ago \| parent \| prev [-]
		You don't need a tester to detect this (and it's not about cables).