This screen showed classification chips and no explanation. iOS has carried one all along, under a comment claiming both apps use the same words. They now genuinely do.
The last sentence is the boundary: a level decides who can open a file, not where it can be put. Neither app stops somebody filing sensitive material somewhere low, and saying so is the honest half of android#15.
Also repairs a doc comment the emoji sweep truncated, which left the test reading "the -property is NOT enforced".
Tests: 731, 0 failures, counted from the result XML.
This screen showed classification chips and no explanation. iOS has carried one all along, under a comment claiming both apps use the same words. They now genuinely do.
The last sentence is the boundary: a level decides who can open a file, not where it can be put. Neither app stops somebody filing sensitive material somewhere low, and saying so is the honest half of android#15.
Also repairs a doc comment the emoji sweep truncated, which left the test reading "the -property is NOT enforced".
Tests: 731, 0 failures, counted from the result XML.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This screen showed classification chips and no explanation. iOS has carried one all along, under a comment claiming both apps use the same words. They now genuinely do.
The last sentence is the boundary: a level decides who can open a file, not where it can be put. Neither app stops somebody filing sensitive material somewhere low, and saying so is the honest half of android#15.
Also repairs a doc comment the emoji sweep truncated, which left the test reading "the -property is NOT enforced".
Tests: 731, 0 failures, counted from the result XML.
mentioned in commit
9b4628a5d3