docs(docs): J1: iPhone deferred by the owner, stays not tested; computer run reported without failure
This commit is contained in:
1 parent
769544a1e8
commit
73706c074e
3 files changed
+14
-10
No files matched your search
@@ -1403,11 +1403,12 @@ not reproduce).
|
||||
|
||||
J1 device run (2026-10-18, `R4_J1.md`, owner decisions BDR-059: both
|
||||
WebKit reserves accepted provisionally, PDF cap kept at 50 MiB): the owner
|
||||
reports the functional checks they executed as passed, no failure. The
|
||||
device list, versions, the checks covered per device, the timings (J1.8,
|
||||
J1.12) and the memory observations (J1.9, J1.10) are recorded in
|
||||
`R4_J1_RESULTS.md` as the owner confirms them; until then they are not
|
||||
claimed here. Headless engines never stand for Safari or a phone.
|
||||
reports the functional checks they executed on a computer as passed, no
|
||||
failure; iPhone / Safari iOS could not be run and is deferred, so it stays
|
||||
not tested and the final acceptance of R4.3 waits for it (OD-6). The
|
||||
browser and version, the checks covered, the timings (J1.8, J1.12) and the
|
||||
memory observations (J1.9, J1.10) are recorded in `R4_J1_RESULTS.md` as the
|
||||
owner confirms them. Headless engines never stand for Safari or a phone.
|
||||
|
||||
Residual risks and open points (R4.3, for the J1 checkpoint):
|
||||
|
||||
|
||||
Reference in new issue
Block a user