3 ms·
Viewing the source shows an html page without a closing body nor html tag: it's probably not the best case for showcasing it seems. The layout it all over the
by cmroanirgo 7y ago
Viewing the source shows an html page without a closing body nor html tag: it's probably not the best case for showcasing it seems.
The layout it all over the place too using FFox, (it's fine on Chrome and Safari) so it also seems to be lacking in some basic cross browser testing, which again, is not good news when show-casing a framework, as a frameworks' prime responsibility is to ensure cross browser/platform uniformity.
Hopefully this all boils down to a simple 'oopsie' in your project, rather than svelte.
- woutr_be 7y ago> Viewing the source shows an html page without a closing body nor html tag It's actually not required to close those tags, the browser will interpret them correctly. (You can see this when inspecting the elements on the page, not just the raw source)
- currysausage 7y agohttps://html.spec.whatwg.org/multipage/syntax.html#optional-tags https://html.spec.whatwg.org/multipage/syntax.html#optional-...
- slantyyz 7y agoIf you use Svelte with Sapper, you will get the "best of both worlds". The first page you hit has the content baked into the HTML, and all subsequent content "pages" load like a single page app. [1] https://sapper.svelte.dev/ https://sapper.svelte.dev/
- NetOpWibby 7y agoInteresting, Firefox is my main browser and it's always looked fine to me. I also built https://socii.network https://socii.network in Svelte/Sapper but that's in need of a rewrite. Just a smidge.