为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Local Website with Local Excel Files Open As Read-Only

  • 5 个回答
  • 1 人有此问题
  • 12 次查看
  • 最后回复者为 dlohse

more options

Hi guys,

We're having an issue opening our local files through Firefox. We have an old local html website that we use to manage reports in excel we have saved to our local server - all of which opens through the file:///... We use Open with.. to open them, refresh the data, then save them. Since last week, Open with.. has been saving them to temp folder and opening them as read only. Is there any way to change this back?

Thanks, D

Hi guys, We're having an issue opening our local files through Firefox. We have an old local html website that we use to manage reports in excel we have saved to our local server - all of which opens through the file:///... We use Open with.. to open them, refresh the data, then save them. Since last week, Open with.. has been saving them to temp folder and opening them as read only. Is there any way to change this back? Thanks, D

所有回复 (5)

more options

"Open with..." is an add-on? I suggest checking with the developers of that add-on as to whether this is a known issue with their add-on in Firefox 96 and whether there is a known workaround.

more options

Files opened in external application via the "Open with" dialog are saved to the OS temp folder and are set to read-only as a safety measure as you may lose edits if you re-safe the file to the same temp folder location.

more options

Open with.. is how you open the file instead of saving it. It is not an addon.

If this is a new safety measure, why wasn't it in the release notes? Also, that doesn't answer my question about how to change it back.

Thanks, D

more options

Normally links to file:/// URLs in http(s):// pages don't work at all, so it's possible no one tests that configuration during the alpha/beta cycle.

You can run a Mozregression to determine which patch changed the behavior. That does require time and bandwidth, but otherwise, you just need to specify the last good release version number (presumably 95) and first bad release version number (presumably 96 but you could use 97 just in case 96 misses the .0.1 through .0.3 releases), and test each build as it is downloaded.

See: https://mozilla.github.io/mozregression/

more options

Bump - has anyone else had this problem and been able to solve it?

Thanks, D