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 Browser Support #1120

Open
AlpayC opened this issue Oct 7, 2023 · 3 comments
Open

Safari Browser Support #1120

AlpayC opened this issue Oct 7, 2023 · 3 comments

Comments

@AlpayC
Copy link

AlpayC commented Oct 7, 2023

🚀 Feature Request

📝 Description

In the current version of Responsively, websites are emulated using only the Chrome browser. As we know, the rendering and behavior of websites can vary between browsers, and many users and businesses also utilize the Safari browser. Hence, having only Chrome does not give a complete picture of a website's responsiveness across popular browsers.

✨ Describe the solution you'd like

I propose the addition of the Safari browser to the Responsively app. This would enable users to check and optimize their website's responsiveness specifically for Safari, ensuring that their designs and features work seamlessly across both Chrome and Safari browsers. By offering this, we can offer a more comprehensive tool for web developers to test their sites on.

✍️ Describe alternatives you've considered

Using external tools: One could use separate tools or emulators to check the responsiveness on Safari. However, this requires switching between multiple platforms, which is not efficient.

Physical device testing: Another alternative is to physically test on a device with Safari. While this gives accurate results, it's not always feasible due to hardware constraints and can be time-consuming.

Integrating Safari emulation directly into Responsively would provide a unified and efficient experience for web developers.

@SHIKHER09
Copy link

hello , can i work on this ??

@manojVivek
Copy link
Collaborator

Technically, the feasibility of this feature is a question, as the whole app runs on Electron (thus Chromium).
But would be happy if you want to try giving a shot if you have any ideas.

@FleetAdmiralJakob
Copy link

Would be nice to see this since I really need to fix Safari issues from my users

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants