Bugzilla

### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR consideration**: support macOS 11
* **User impact if declined**: FF 68.x not working on macOS 11
* **Fix Landed on Version**: 80
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: Limited to macOS platform. Only affects loading of library files from /System/ and /usr/lib/. Should Firefox attempt to load a library from a system location, but that library doesn't exist in that exact location, but a library with the same name exists elsewhere on the system, then loading will succeed. It's only a problem if Firefox expects that the loading of the system library in a nonexisting location returns a failure. It seems unlikely that Firefox depends on this behavior for system libraries.
* **String or UUID changes made by this patch**: none

### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR consideration**: support macOS 11
* **User impact if declined**: FF 78.x not working on macOS 11
* **Fix Landed on Version**: 80
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: Limited to macOS platform. Only affects loading of library files from /System/ and /usr/lib/. Should Firefox attempt to load a library from a system location, but that library doesn't exist in that exact location, but a library with the same name exists elsewhere on the system, then loading will succeed. It's only a problem if Firefox expects that the loading of the system library in a nonexisting location returns a failure. It seems unlikely that Firefox depends on this behavior for system libraries.
* **String or UUID changes made by this patch**: none