Sorry if I wasn't clear. I meant the WebKit guidelines were from the commenter, not from the apple page.
> or features that improve memory safety within other languages, within the alternative web browser engine at a minimum for all code that processes web content;
This can't be analyzed in any real way, so its just another way that Apple will restrict web engines and claim it was due to "not enough use of memory safety language features"
Why does it matter if Apple themselves don’t link the WebKit docs? It’s literally their project and seems to meet their requirements.
There’s a lot of things in the requirements like funding that Apple cannot verify. I think you’re being too binary in this.
Some of it is very clearly intended to be a “show us you are at least considering these security measures and have practices in place to minimize known issues”. Again, for the third time, it’s clearly NOT a list for ongoing perfect security, given that there are other items on the list that deal with further mitigation strategies.