Is this an issue in Cesium or the sample model? https://github.com/KhronosGroup/glTF-Sample-Models/pull/12
@lasalvavida can you please look at this after the 1.1 updates? Or anyone else in the meantime...
Could be the same issue three.js had, https://github.com/mrdoob/three.js/pull/10319.
Looks exactly the same as the three.js bug (stuff of nightmares).

@denverpierce thanks for looking into it. Any chance you have the bandwidth to try out the same type of fix used in three?
Yeah, if it's a straightforward one liner like three.js I should be able to take a look at it.
That would be great, thanks!
I crunched on this a bit but couldn't make any progress. Is the gltf spec the best resource to look at for this issue?
Thanks for investigating, @denverpierce! I suspect the fix to three.js, https://github.com/mrdoob/three.js/pull/10319, would be the best place to look, perhaps followed by the reference card, and then the spec.
Change if (defined( to if (!defined( at https://github.com/AnalyticalGraphicsInc/cesium/blob/389cb1d3664536c53755b62a297bd96400abaff8/Source/ThirdParty/gltfDefaults.js#L404
@cx20 the fix for this will be in Cesium 1.29, which will be released on Monday. Can you please update gltf-test?
I will update it as new version is released :)
I confirmed that WalkingLady glTF model is displayed in Cesium.js 1.29.
https://github.com/cx20/gltf-test

Great, thanks for the quick response, @cx20!
Thanks to @javagl for the fix!
Most helpful comment
I confirmed that WalkingLady glTF model is displayed in Cesium.js 1.29.
https://github.com/cx20/gltf-test