testing/web-platform/meta/portals/portals-post-message.sub.html.ini


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

[portals-post-message.sub.html]
  [cannot call postMessage on portal without portal browsing context]
    expected: FAIL

  [postMessage message received by portalHost in cross-origin portal]
    expected: FAIL

  [postMessage received by portal host in cross-origin portal when target origin is specified]
    expected: FAIL

  [postMessage message received by portalHost]
    expected: FAIL

  [postMessage after activate throws error]
    expected: FAIL

  [message should not be delivered to cross-origin portal when targetOrigin is not specified]
    expected: FAIL

  [message should not be delivered to portal when targetOrigin does not match]
    expected: FAIL

  [postMessage before activate should work and preserve order]
    expected: FAIL

  [postMessage received by portal host in same-origin portal for multiple valid target origins]
    expected: FAIL

  [postMessage during activate throws error]
    expected: FAIL

  [postMessage with includeUserActivation]
    expected: FAIL

  [postMessage with array buffer without transfer]
    expected: FAIL

  [postMessage with message ports and cross-origin portal]
    expected: FAIL

  [postMessage with transferred array buffer]
    expected: FAIL

  [postMessage with message ports and same-origin portal]
    expected: FAIL

  [postMessage should fail with invalid ports]
    expected: FAIL

  [postMessage with message object]
    expected: FAIL

  [postMessage should fail if message serialization fails]
    expected: FAIL