You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you add Safari for visionOS and Safari for iPadOS to the browsers available to compare?
visionOS has differences regarding WebXR support. You can also see the feature flags by using the visionOS simulator.
iPadOS supports Fullscreen API by default. iOS has it as a feature flag.
There are most likely other differences as well. Having a visionOS browser compare would be more impactful than the iPadOS one, but having a iPadOS one would be nice too.
Also: Renaming Safari to "Safari for macOS" would be a good QOL change, just like there is a "Safari for iOS".
The text was updated successfully, but these errors were encountered:
I've been expecting that at some point Can I Use will want to add a column for Safari on visionOS — perhaps alongside Wolvic and the Meta Quest browser. Currently there is a 'desktop' section, and a 'mobile' section. Perhaps it's time for a third section.
This makes sense to us. There are features that will be supported in visionOS that are not supported in iOS. I'm happy to help confirm data.
I’m in favor here. There are several devices with their own browsers, and even when VR browsers are forked from desktop or mobile browsers, in terms of feature sets they tend to diverge fairly quickly. We’ve seen that with Wolvic, and as Jen says, also with visionOS Safari.
Could you add Safari for visionOS and Safari for iPadOS to the browsers available to compare?
visionOS has differences regarding WebXR support. You can also see the feature flags by using the visionOS simulator.
iPadOS supports Fullscreen API by default. iOS has it as a feature flag.
There are most likely other differences as well. Having a visionOS browser compare would be more impactful than the iPadOS one, but having a iPadOS one would be nice too.
Also: Renaming Safari to "Safari for macOS" would be a good QOL change, just like there is a "Safari for iOS".
The text was updated successfully, but these errors were encountered: