where it should move on to the next slide, it just flashes and the next slide is there. There’s no smooth transition. It’s probably mostly a memory issue or performance issue. But it’s just annoying to see that something used to work and doesn’t work any longer. Since we’re doing a lot of WebGL stuff we have to recommend that everyone that uses our website uses Firefox, because it is just not performant on Chrome, sorry. I guess it works, it’s just you can’t really get up to 60 frames per second, especially with a lot of entities and assets being deployed. I don’t know if it’s specifically CesiumJS or if it’s my code, I haven’t done a strict A/B testing. We’ve just seen that Firefox seems to be a lot more performant. So we definitely recommend Firefox over Chrome, but Chrome works and, you know, a lot of people use it so we don’t really say “don’t use it,” we just, if we have a chance we recommend Firefox. For this specifically, for the algorithms we have to run and for WebGL, I think some of it is also WebAssembly with CesiumJS specifically, some of the workers to load in textures, those are a lot more performant on Firefox for some reason.
Issues with requestAnimationFrame timing also came up in two interviews, see appendix F .
Forms In the survey responses, forms ranked #4 for both overall feature areas and layout/styling features causing issues. For this report we did not look closer at this area.
Web developer quotes Some quotes from the survey responses:
Form components do not look and work the same. Styling form components does not work the same. Especially the more complex components like range. most interactive elements (i.e. date inputs, select dropdowns) get styled by each browser differently and neither of them give you much freedom in styling.
Made with FlippingBook - professional solution for displaying marketing and sales documents online