Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

safari support + low-latency local files sync improvement #886

Open
edenvidal opened this issue Dec 22, 2024 · 8 comments
Open

safari support + low-latency local files sync improvement #886

edenvidal opened this issue Dec 22, 2024 · 8 comments
Assignees

Comments

@edenvidal
Copy link
Member

edenvidal commented Dec 22, 2024

the app works perfectly in chrome (press "o" to open a site folder), using technologies that ensure browser compatibility. we can either improve its functionality for safari or redesign the file system to support cross-browser compatibility, leveraging newer technologies that weren’t considered before.

for low-latency local file sync, we need better sync triggers and improved handling of changes to assets and media files.

@edenvidal edenvidal converted this from a draft issue Dec 22, 2024
@kareem-g
Copy link
Contributor

@edenvidal I currently don't have access to macOS for testing on Safari.

@edenvidal
Copy link
Member Author

@kareem-g not sure how we can do it then. we'll see

@edenvidal
Copy link
Member Author

@atulbhatt-system32 need your help with optimisations here

@atulbhatt-system32
Copy link
Contributor

@edenvidal we will have to breakdown this into multiple steps:

  1. Understand limitations with current implementation.
  2. Find if there are ways to overcome this limitation and if something new is out there that can solve it.
  3. If something new is not there than can we make something of ours or is the limitation is at core level that is to say limitations from the browser.

So ultimately we will have to breakdown this task into as many small steps as possible and then give estimation on the smallest step instead of giving it for the entire task.

Consider it this way. We can't see what's our next step is without knowing the result of our current step.

@edenvidal
Copy link
Member Author

@atulbhatt-system32 accepted. please include the obvious first step + possible arising 2,3, steps in your quote?

@atulbhatt-system32
Copy link
Contributor

@edenvidal

The first obvious step is to research on where we stand in our current cross-browser compatibility and find ways to improve it.

Now the next step would be the choose the one with optimum tradeoffs because there are going to be some tradeoffs is what my intuition says.

So I can't give your entire quote for it.

@edenvidal
Copy link
Member Author

edenvidal commented Feb 18, 2025

@atulbhatt-system32 consider the safari support a quick research and decision making.
then anyway need to improve the sync and its triggers for the perfect local-sync experience. for example, updated assets in the local folder won't show or considered in the actively rendered page.

@atulbhatt-system32
Copy link
Contributor

Image

So no there are limitations even with ponyfill. So we won't be able to provide support on safari.

@edenvidal edenvidal moved this from Idea to Next Up in rnbw 0.1 Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next Up
Development

No branches or pull requests

3 participants