Is it only for me that the `appFrame` menu does no...

# fritz2

[Hampus Londögård]

Is it only for me that the appFrame menu does not extend when pressed if using mobile?

[Christian Hausknecht]

Which version fo fritz2 do you use?
And (probably more important): Which version of fritz2-template did you use to start your project?

We have fixed an issue with our delivered``index.html`` of the template not long ago: https://github.com/jwstegemann/fritz2-template/pull/7

Is this probably the solution for your problem?

If not, which mobile device does not work? Or how do you reproduce this behavior?

Be aware on top, that the ``appFrame`` has only sneaked into the core code for some internal reasons. It is quite unmature right now and iirc has not yet been announced for public usage. So be warned, that we have quite some things to polish and rework for this component!

But of course you are welcome to test it out and give feedback to us. We appreciate this a lot :-)

[Hampus Londögård]

0.10, the mobile variant in dev-tools (Edge Chromium to be specific)

I also noted that fritz2 don’t work with Kotlin 1.5 at all really.
I’ll take a look at the fix later today. I’m a big fan of the appFrame 🙂

Btw, looking at the log it seems like it could be a CSS related issue. Getting a few error-msg:s related to that.
Haven’t deep-dived as I focused on content/functionality related to the core of my PWA rather than details/looks

[Christian Hausknecht]

I’m a big fan of the appFrame 🙂

Thx. We will improve this in the near future to make it stable and presentable :-)

[Hampus Londögård]

My index.html was fine 🙂
partyplanner.js?bdcc:54002 unable to insert rule in stylesheet: Failed to execute
Getting a few of these (3-4)

[Hampus Londögård]

Seem related to t new AppFrameComponent & at Styling.addDynamicCss

[Hampus Londögård]

Is it perhaps problematic that the !important has no space to the actual value? E.g.
Failed to parse the rule '.@media (max-width: 48em){left:0!important;opacity:1!important;}'

[Jan Weidenhaupt]

I also noted that fritz2 don’t work with Kotlin 1.5 at all really.

I created an issue for that (https://github.com/jwstegemann/fritz2/issues/389). It seems that some of our libraries we depend on are not on Kotlin 1.5 compatible yet and therefore the code generation of fritz2 @Lenses is not working right now. We will investigate on that and can hopefully find a solution to support Kotlin 1.5 soon as possible.

[Jan Weidenhaupt]

Is it perhaps problematic that the !important has no space to the actual value? E.g.

Failed to parse the rule '.@media (max-width: 48em){left:0!important;opacity:1!important;}'

I fixed the problem and created the followoing issue: https://github.com/jwstegemann/fritz2/pull/390

[Hampus Londögård]

Cool! Thanks.

So the issue was that the cssString was supposed to be first input, rather than secondary?
I guess adding a typealias, value class or something for the CSS could make sense to make sure refactoring don’t break things like this where you have dual string-inputs

[Jan Weidenhaupt]

Yeah right, this was the problem. An alias is a good idea and we will keep that in mind!