On Sat, Jan 04, 2020 at 12:53:23PM +0900, Bryan Linton wrote: > Hello ports@ > > After upgrading to Firefox 71, I was no longer able to input > Japanese due to the newly-added unveil and pledge support. After > some debugging, I found that adding the following lines to > /etc/firefox/unveil.main allowed me to input Japanese as usual. > > ---------8<---------- > --- /usr/local/lib/firefox/browser/defaults/preferences/unveil.main Sat Dec > 21 15:08:23 2019 > +++ /etc/firefox/unveil.main Fri Jan 3 12:25:53 2020 > @@ -3,6 +3,12 @@ > /dev/video rw > /dev/video0 rw > > +# for launching the anthy input method from uim > +/etc/anthy-conf r > +~/.anthy r > +~/.tomoe r > +~/.uim.d r > + > /etc/fonts r > /etc/machine-id r > ---------8<---------- > > However, this raises some interesting questions. How far down > this path do we want to go? The above patch enables the UIM+Anthy > combination to work again, but what about SCIM+Anthy? Ibus+Anthy? > SCIM+Pinyin? There are 26 ports in ports/inputmethods; do all of > them get added to unveil.main? > > While I'm aware that adding every possible contingency to unveil > largely defeats its purpose, I'm also concerned that the > alternative would be users simply disabling pledge+unveil > entirely if they find that they can no longer input CJK text. > > Which then brings us full circle to the security model of unveil > being defeated... > > That being the case, perhaps adding a short blurb like the > following to Firefox's pkg-readme would be a better way to go.
I dont have a preference between those, and i'm fine with each of them.
