Making myself happy by stripping out loads of JS and replacing it with declarative markup and modern CSS, which will work in modern (evergreen) browsers, and Safari too.
@owa@brucelawson interesting, most of those comments have little to no detail. I’d love to read some real world issues with Safari. I use it as my main browser and develop for it daily.
@cdevroe@brucelawson More Recently:
JS-driven animations capped to 60fps (30fps in low-battery mode); various bugs affecting the performance of GPU-accelerated animations (presence of scroll containers; translating slightly large layers; frame drops in some situations when using basic CSS animations or WAAPI; bad layer painting in random situations; animations entirely skipped in others); 3D transforms and z-index not working as spec;
@cdevroe@brucelawson and a wide variety of bugs affecting the resizing of the visual viewport and scrolling of the page in reaction to onscreen keyboard appearance on iOS.
All of this is because of underfunding for over a decade caused by a lack of competition... OWA will try to fix the competition aspect, which will lead to funding, which will lead to a reliable platform for building apps.
@cdevroe@brucelawson This is just one example of many, and part of the reason we formed OWA. Bugs in Safari make it very difficult to build UIs that are equivalent in quality to their native counterparts. Ignoring JS APIs or missing features, Safari is the hardest browser to build for, simply because it has many long standard bugs that aren’t addressed.
Add comment