Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

pax-eterna

macrumors regular
Original poster
Just (for the first time on MacOS) tried to load an online editing app in Safari and got this message

"This browser is not supported or you are using mobile. The BBMO is only supported on desktop using the latest Google Chrome, Microsoft Edge, Opera and Vivaldi browsers.

If you are using Safari or Firefox, consider writing to Apple Support or Firefox Support and asking them to allow Filesystem API on directories."

asking for opinions here please : is it worth time to bother to write to Apple about this? Or does anyone have any inkling of if Apple may look to allow this in a future release already?

Thanks IA
 
asking for opinions here please : is it worth time to bother to write to Apple about this? Or does anyone have any inkling of if Apple may look to allow this in a future release already?
What version of macOS? What version of Safari? Looks like Safari does have support -
 
What version of macOS? What version of Safari? Looks like Safari does have support -

haha, now the inevitable question, how do I turn it on? As this app reports it is not available, I am assuming it is off by default OR do I need to install some third party app, perhaps?
 
haha, now the inevitable question, how do I turn it on? As this app reports it is not available, I am assuming it is off by default OR do I need to install some third party app, perhaps?
Perhaps the issue is the "online editing app". Perhaps it hasn't been updated since before Safari supported the File System API. It could be simply checking the browser version, rather than File System API support availability, and presenting the message. Throw it back at the "online editing app" developer.
 
  • Like
Reactions: NoBoMac
Perhaps the issue is the "online editing app". Perhaps it hasn't been updated since before Safari supported the File System API. It could be simply checking the browser version, rather than File System API support availability, and presenting the message. Throw it back at the "online editing app" developer.

Yes I think you are correct there, and I have done exactly that!
Thanks again for your help 👌
 
Issue has been around for a while now. Here's a post on the app's forum from January 2025 complaining.

Lots of poorly, imo, written info out there about the API and near as I can tell, not a lot of hope Apple will do a full implementation. Looks like Apple has implemented it for private/sandboxed file access only and not allowing access to the bigger filesystem, probably due to a security risk to allow a web page to have full access to one's device.

(Seems like it started life as an API for cross-browser private storage read/write and has morphed over time to be a bigger cross-browser way to do more than private read/writes)

And spotted this bit under some documentation for the API. Since not standard, more reason for Apple to not do anything about this. A lot of people that work for Google are working on this project so no surprise that they have their own hook implemented in their browser.

This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.
 
  • Like
Reactions: pax-eterna
WebKit Features in Safari 26.0
https://webkit.org/blog/17333/webkit-features-in-safari-26-0/
"There’s also now support for the File System WritableStream API, enabling direct writing to files within the user’s file system. This API provides an efficient and streamlined way to save data, allowing developers to build applications with enhanced file handling capabilities, such as direct downloads and in-place file editing."

With "Show features for web developers" enabled in Safari - Settings - Advanced, there are additional settings:
in Developer - Security - Disable local file restrictions & Disable cross-origin restrictions
in Feature Flags "File System WritableStream" &"Allow universal access from file:URLs"

"Show features for web developers" also allows changing Safari's user agent to Chrome or Edge from the Develop menu.
 
WebKit Features in Safari 26.0
https://webkit.org/blog/17333/webkit-features-in-safari-26-0/
"There’s also now support for the File System WritableStream API, enabling direct writing to files within the user’s file system. This API provides an efficient and streamlined way to save data, allowing developers to build applications with enhanced file handling capabilities, such as direct downloads and in-place file editing."

With "Show features for web developers" enabled in Safari - Settings - Advanced, there are additional settings:
in Developer - Security - Disable local file restrictions & Disable cross-origin restrictions
in Feature Flags "File System WritableStream" &"Allow universal access from file:URLs"

"Show features for web developers" also allows changing Safari's user agent to Chrome or Edge from the Develop menu.

So if I go to that location and change to reflect the above, will that work do you think?
 
I don’t have Tahoe installed on a Mac, I’ve tested https://bbmo.singularsound.com in a virtual machine with Tahoe 26.4.1 Safari 26.4 and it didn’t work.

They might be blocking Safari without even checking if the functionality is available. You could ask on their forum or support email support@singularsound.com
yeah already done, thanks. They accepted the suggestion and will look at it. So that clears Tahoe of blame at least 🙂
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.