Replies: 1 comment 11 replies
-
Yeah, its a false impression, builder != "your site", its a good idea to mention it there, I saw several people jumping to the wrong conclusions too! |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
While there are FLO versions of the proprietary Google Chrome (e.g.
ungoogled-chromium
), Firefox is the browser of choice for many privacy and FLO advocates and I expect the sites I build to be able to work consistently across browsers - in fact the design tool is a great place to limit features to those supported cross-browser and cross-platform.As it currently stands with Webstudio only supporting Blink-based browsers, I naturally get the (hopefully false) impression that the site I'm designing can only be relied on to look/work as expected in those same browsers.
Perhaps it's just the app's UI that is Chrome-specific and the tool's output is cross-browser, but when cross-browser support is not targeted early on it's often the case that browser-specific features creep in that need to be substantially refactored when the decision to support more browsers is finally made, so the time saved upfront is often not worth it...
Anyway, if other browsers are targeted with Webstudio's output, I suggest mentioning that in the tool's not-supported error message, such as:
Beta Was this translation helpful? Give feedback.
All reactions