* Add a test to confirm that the ResourceLoader::respond() logic works as intended. * Remove the client code for preventing it from being loaded. This can never happen in production unless there is a bug. Instead of optimising to avoid a pointless request that only happens when the software is broken, instead optimise for when the software is not broken by just letting it happen. The server already handles it just fine. This was originally added in 2015 with |
||
|---|---|---|
| .. | ||
| common | ||
| integration/includes | ||
| parser | ||
| phan | ||
| phpunit | ||
| qunit | ||
| selenium | ||
| .htaccess | ||