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

PWA webmanifest missing from select pages #8455

Closed
4 tasks done
brianramseyau opened this issue Jan 24, 2024 · 4 comments
Closed
4 tasks done

PWA webmanifest missing from select pages #8455

brianramseyau opened this issue Jan 24, 2024 · 4 comments
Labels
fixed Bugs that are fixed (in a coming release).

Comments

@brianramseyau
Copy link

Support guidelines

I've found a bug and checked that ...

Description

I have noticed that some (perhaps newer?) pages do not include the webmanifest for PWA support.

These include pages such as Login and Dashboard (which, are kind of the most important to have this present IMO). Other pages such as Bills or Budget present the manifest just fine.

This is potentially just an oversight of a/the (new?) templating system where it doesn't have the include such is present in

<link rel="manifest" href="manifest.webmanifest?v=3e8AboOwbd">

Potentially splitting the manifest link tag into a separate partial and including it in the PWA template also (https://github.com/firefly-iii/firefly-iii/blob/ec59f80fe3c18d408382e4916dec9d95eb45b556/resources/views/pwa.twig)? or further down the chain in the system itself...

Debug information

Present up to and including v6.1.7

Expected behaviour

PWA manifest to be presented with all pages, including login and dashboard.

Steps to reproduce

No response

Additional info

No response

@JC5
Copy link
Member

JC5 commented Jan 25, 2024

The webmanifest is present on the dashboard. This is easy to verify on the demo site. What makes you think it isn't?

The fact that it's not present on the login and register pages is correct, and that's easily fixable.

JC5 added a commit that referenced this issue Jan 25, 2024
@JC5 JC5 added bug fixed Bugs that are fixed (in a coming release). labels Jan 25, 2024
@JC5 JC5 added this to Firefly III Jan 25, 2024
@JC5 JC5 moved this to Done in Firefly III Jan 25, 2024
@JC5 JC5 added this to the firefly-iii-v6.1.8 milestone Jan 25, 2024
@brianramseyau
Copy link
Author

brianramseyau commented Jan 25, 2024

Thanks for the prompt reply @JC5

The Demo site appears to be on the V1 dashboard, not the V2 one... this is why, I expect, it's not aligned with my V2 findings.
While I understand V2 is a WIP, this is, I feel a valid point to raise (early)

I also understand I missed this vital piece of information in my original report, and I apologise

@brianramseyau
Copy link
Author

This is a screenshot of the network loaded assets on the v2 dashboard on my instance, for context
image

Copy link
Contributor

Hi there!

This is an automatic reply. Share and enjoy

It seems your issue is about the new v2-layout that is currently in development for Firefly III.

These issues are collected in a GitHub discussion.

Please note that the v2 layout is still very much in development.

Thank you for your contributions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2024
@JC5 JC5 removed this from Firefly III Aug 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
fixed Bugs that are fixed (in a coming release).
Projects
None yet
Development

No branches or pull requests

2 participants