Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

q-layout issue on iOS safari #422

Closed
stephentuso opened this issue Feb 28, 2017 · 3 comments
Closed

q-layout issue on iOS safari #422

stephentuso opened this issue Feb 28, 2017 · 3 comments
Milestone

Comments

@stephentuso
Copy link
Contributor

I have a template similar to this:

<q-layout>
  <div slot="header" class="toolbar">
    ...
  </div>

  <div class="layout-view">
    <q-infinite-scroll>
      ...
    </q-infinite-scroll>
  </div>
</q-layout>

This works fine in desktop browsers and Android, but on iOS 9 Safari the content of the infinite scroll is covered by the toolbar. I'm using a flexbox based grid in the infinite scroller. Is this an issue with the framework? Or could there be something wrong on my end?

@rstoenescu
Copy link
Member

Already fixed in future v0.13.2 or edge version. Can you confirm with edge version? http://quasar-framework.org/guide/quasar-nightly-build.html

@rstoenescu rstoenescu added this to the v0.13.2 milestone Mar 1, 2017
@stephentuso
Copy link
Contributor Author

@rstoenescu I installed the edge version and I'm still having the same issue. Works on iOS 10.2 but not on 9.3. Doesn't q-layout just use flexbox? Seems like iOS 9.3 is missing support for something, but according to caniuse, flexbox should be fully supported. I'm trying to inspect it to get some more details but I'm having issues with Safari's remote debugger.

@rstoenescu
Copy link
Member

Please do help. Need some assistance as I'm currently focusing on v0.14. Layout component indeed uses flexbox and theoretically it should just work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants