You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.
Hey @chadian, do you have suggestions how this could be theoretically possible, given that FastBoot render does not know viewport dimensions?
I wish browsers sent viewport size in HTTP headers, but that's not the case.
The only idea I have is to have inline JS in the HTML that would execute eagerly and redirect to the same page but with extra query params indicating viewport size. But this may cause a delay defeating the purpose.
<FillUp
@breakpoints={{hashsmall=(fill-up-between0800)
medium=(fill-up-between8001200)
large=(fill-up-gte1200)
}}
as |F|>
{{#ifF.breakpoints.fastboot}}
👋Here's some basic useful information, until I can re-render.
{{/if}}
</FillUp>
This way you're opting in for what gets rendered in fastboot environment with some minimally useful information or a loading spinner.
I'm curious about your idea though. If you did know the global viewport dimensions how would you know the the size of the local components? Is there a use-case where supplementary details wouldn't suffice until the app has had a chance to render?
Support FastBoot so that this addon:
The text was updated successfully, but these errors were encountered: