I can’t think of a single time since we released the first web framework 10 years ago that we ever had to suddenly put out a new release because apps were broken by an update to a popular web browser.
Remember that (as has already been stated) browsers are standards-based and a Xojo web app spits out HTML, JavaScript, and CSS behind these scenes just like one written directly using those technologies.
A desktop app is far more likely to suddenly “break” due to some OS update (though that too is rare) than a web app breaking due to a browser update.
The MORE likely scenario would be that you can’t yet move your app from Web Framework 1.0 to 2.0 and while adding functionality you encounter a new bug that cannot be worked around. This too seems very unlikely but theoretically it could happen.
Most users can move their apps to Web Framework 2.0 but we realize that there are a few missing functions that a some users require. We are working on adding those so all users can move their projects if and when they wish. I know that for some of you, you’re feeling caught in the middle and that’s understandable. I think the risk of their being a bug you can’t workaround prior to being able to move to Web Framework 2.0 is very low but should it happen, we are here to help you figure out a solution.
Keep in mind that some won’t and probably should not move their apps. If I had a large web app that was working fine and was likely to reach the end of its life in the next 5 years, moving it to Web Framework 2.0 would not be an attractive option. However, if I didn’t know how long it would be in use and liked some of the benefits of Web Framework 2.0, I’d be considering it.