Back

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
 
 
 
 
 
 
 
 
 
 
 
 
 
 
5x
 
 
 
 
 
 
 
 
 
 
 
 
 
82x
 
 
 
 
 
 
 
 
 
 
 
 
 
 
18x
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
17x
17x
68x
 
 
 
 
/**
 * File builders for anything that goes through the dropzone's accepted-file
 * filter (`components/upload-dropzone/video-files`). That filter reads a file's
 * leading bytes and checks them against the container its extension claims, so
 * a test file built from `[ 'x' ]` is no longer a video no matter what MIME
 * type it is given — the byte content has to be right.
 */
 
import { act } from '@testing-library/react';
 
// A minimal ISO-BMFF header: a 24-byte `ftyp` box branded `isom`. Enough for
// the container check, which reads the box type at offset 4; the rest of a real
// mp4 (moov/mdat) is irrelevant to it. Covers .mp4, .m4v, .mov and the 3gp
// family, which share the format.
const ISO_BMFF_HEADER = new Uint8Array( [
	0x00, 0x00, 0x00, 0x18, 0x66, 0x74, 0x79, 0x70, 0x69, 0x73, 0x6f, 0x6d, 0x00, 0x00, 0x02, 0x00,
	0x69, 0x73, 0x6f, 0x6d, 0x69, 0x73, 0x6f, 0x32,
] );
 
/**
 * A file that really is the video its name claims: correct container bytes,
 * so it survives the dropzone filter end to end.
 *
 * @param name - File name, including the extension.
 * @param type - Reported MIME type. Defaults to `video/mp4`.
 * @return The file.
 */
export function makeVideoFile( name: string, type = 'video/mp4' ): File {
	return new File( [ ISO_BMFF_HEADER ], name, { type } );
}
 
/**
 * The bug both testers reproduced: a text file renamed to a video extension.
 * Chromium derives `File.type` from the extension, so this reports `video/mp4`
 * exactly as the real thing does — which is why the default type here is
 * `video/mp4` and not `text/plain`. Only the bytes give it away.
 *
 * @param name - File name, including the (video) extension.
 * @param type - Reported MIME type. Defaults to the `video/mp4` a browser
 *             would report for a `.mp4` name.
 * @return The file.
 */
export function makeRenamedTextFile( name: string, type = 'video/mp4' ): File {
	return new File(
		[ 'This is a plain text file that somebody renamed. It is not a video.\n' ],
		name,
		{ type }
	);
}
 
/**
 * Let the accepted-file filter settle after a drop or a pick. It reads each
 * file's header, so the hand-off to `onFiles` — or the refusal notice — lands a
 * task after the event rather than during it.
 *
 * Four ticks, not two. A REFUSAL now reads the headers twice: once to decide
 * which files survive (`filterVideoFiles`) and once to decide which sentence is
 * true about the ones that didn't (`describeRefusal`). Under jsdom the read goes
 * through `FileReader`, so each pass costs its own macrotask, and a caller that
 * adds an await of its own on top — the Library's `planVideoDrop` — needed more
 * than the two this used to give. Waiting longer than necessary is free; waiting
 * too little is a flake that only shows up on a loaded CI box.
 *
 * Assertions that a notice appeared are still better written with `waitFor`.
 * This is for the tests that want a settled tree before looking at it at all.
 *
 * @return Resolves once the pending file checks have run.
 */
export async function settleFileCheck(): Promise< void > {
	await act( async () => {
		for ( let tick = 0; tick < 4; tick++ ) {
			await new Promise( resolve => setTimeout( resolve, 0 ) );
		}
	} );
}