Jay Oster e375addec6 Fix MIME type support for glTF buffer Data URIs (pipelined) (#3106) ... Apply #3101 on top of the `pipelined-rendering` branch, as requested by @cart in https://github.com/bevyengine/bevy/pull/3101#issuecomment-965907267 # Objective - The glTF 2.0 spec requires that Data URIs use one of two valid MIME types. `bevy_gltf2` only supports one of these. - See: - https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#_media_type_registrations - https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#file-extensions-and-media-types - https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#binary-data-storage > Buffer data **MAY** alternatively be embedded in the glTF file via `data:` URI with base64 encoding. When `data:` URI is used for buffer storage, its mediatype field **MUST** be set to `application/octet-stream` or `application/gltf-buffer`. (Emphasis in original.) ## Solution - Check for both MIME types.		2021-11-11 11:33:33 +00:00
..
src	Fix MIME type support for glTF buffer Data URIs (pipelined) (#3106)	2021-11-11 11:33:33 +00:00
Cargo.toml	Update for edition 2021 (#2997)	2021-10-25 18:00:13 +00:00