Comment 13 for bug 1393515

Oliver, except it's not a phone, it's a converged computing device; I use file:/// browsing in my desktop and expect to be able to do the same when I replace my desktop with my phone, monitor, keyboard, and mouse.

John, I agree that the long run should definitely include an AppArmor profile on the browser and use content hub when trying to browse outside of that. I just wanted to make the case that blocking file:/// access isn't the best way forward, and trying to implement a piece-meal security policy via UI modifications is building technical debt that's better left unsolved rather than handled poorly. Thanks for forcing a clarification.

Thanks