@serg See my complete guide on window height for mobile browsers for the Quasar Framework

@njwade Yes there is. It’s kind of hacky though. Please read this guide.

People at ionic framework have been talking for days about autofocus in ionic, on android and ios.

I was hoping if anyone had some advice for me how to make autofocus work on Quasar Cordova?

Cheers!

@danielo515 @a47ae
I had exactly the same problem with this snippet as you. It worked when I just deleted - ele.scrollHeight from the snippet above.

It works with a helper function like so:

	function scrollToElement (el) {
	  let target = getScrollTarget(el)
	  let offset = el.offsetTop // do not subtract the el.scrollHeight here
	  let duration = 1000
	  setScrollPosition(target, offset, duration)
	}

I also updated the snippet in the Quasar documentation and made my PR here:
https://github.com/quasarframework/quasar-framework.org/pull/649

@eleina A proposal is currently in progress to add the functionality for custom icons:
https://github.com/quasarframework/quasar/issues/2494

Also, in that thread is explained how to create your own icon font, though it be a bit cumbersome…

I’m trying to implement the QTable, but want to edit how the rows / column headers look.

I believe there are two ways which … do the same thing?

• Grid mode:
  https://quasar-framework.org/components/datatable.html#Grid-Mode
• Custom rows:
  https://quasar-framework.org/components/datatable.html#Custom-rows

What is the difference between these two?

So I’m kind of stuck on something:
My entire app is built with a very distinct design and the base of my CSS has always been the iOS theme.

However, for two components I require to use the Material version of the Quasar Material theme, while keeping my iOS theme in tact.

Can anyone point me in the correct direction how I best start writing such a hack, where I’m allowed to choose Material theme for just 1 or 2 components?

The components I need of Material are QTabs and Datetime Picker.

@ssuess Exactly… iOS really f*cked up the PWA support this time…

I believe they want to make the worst compatibility as possible to make devs not use PWA’s and make more native apps. Because Apple won’t make money from PWA’s and they have more chances they will from native apps.

Welcome to the world where money is more important than the consumers.

@ssuess Thanks for your post.
I meant this comment in this post:

What to have in mind
Your PWA won’t keep state between sessions, if the user gets out of a PWA, it will be restarted when coming back, so if you need the user to validate an email, SMS or do a two-factor authentication, have that in mind to offer a proper solution.

It was the same for me, where every time I open the PWA it will flash and take me back to the homepage. Maybe they fixed this already?

Combined with this, not getting the prompt to install the latest service worker and having users using older versions of my apps without me being able to do anything about it just added to the list of problems… That’s why I left PWA’s.