linux-traipu team mailing list archive

[David Elder <1972762@xxxxxxxxxxxxxxxxxx>]

This bug breaks any application that uses firefox to open local files in
/tmp for display. I'd politely suggest that breaking this sort of widely
supported and used functionality for no clear benefit or advantage is
perhaps not the best design choice. This is especially true when users
can simply go out and download other versions that do support this
functionality but may suffer from not being regularly and automatically
updated.

If the issue is security then having an about:config option to pop up a
window for permission to open local files that defaults to ON might be a
better solution which leaves warnings and functionality in the hands of
the user (the feature could be turned off in settings or by accessing
about:config) but defaults to a more secure option for those that will
likely never intentionally open local files.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1972762

Title:
  Firefox and Chromium snaps preventing apps and devices from working
  correctly.

Status in Chromium Browser:
  New
Status in Mozilla Firefox:
  New
Status in snapd:
  New

Bug description:
  Many apps put files in /tmp or ~/.cache to then open those files with
  other apps. Files won't open from those locations with the Firefox
  snap. Just within a few days of using, I've found quite a few apps
  that don't work as they should or seem broken as a result.

  * Any archive manager (xarchive uses /tmp, file-roller and engrampa use ~/.cache, peazip uses ~/.ptmp)
  * Catfish (uses /tmp also for opening files in archives)
  * fish (fish_config uses an html file in /tmp and uses a browser for configuration)

  Other things not working:

  * WebUSB (Used in Chromium for securely interacting with USB devices, installing and updating Android devices, etc)
  * USBMidi (Used in Chromium and Firefox for using Midi instruments)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1972762/+subscriptions