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

Update app manifest to match with actual favicons #2141

Merged
merged 1 commit into from
Nov 4, 2020

Conversation

antgamdia
Copy link
Contributor

Description of the change

Wrong favicon declaration was causing a mismatch and, therefore, a console warning was being thrown: Error while trying to use the following icon from the Manifest: http://localhost:8080/favicon.ico (Resource size is not correct - typo in the Manifest?).

This PR simply declares the existing favicons in the manifest.json.

Benefits

No error is thrown in the console.

Possible drawbacks

N/A

Applicable issues

N/A

Additional information

N/A

Wrong favicon declaration was causing a mismatch and, therefore, a console warning was being throw
Copy link
Contributor

@andresmgot andresmgot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to understand better what's the purpose of this manifest, it sometimes fail to be downloaded but the app is not affected.

@antgamdia
Copy link
Contributor Author

I need to understand better what's the purpose of this manifest,

AFAIK it only contains information to install apps on phones. These icons are supposed to be used when a web app is installed (or pinned) on the home screen of a mobile phone. More info: https://developer.mozilla.org/en-US/docs/Web/Manifest

@antgamdia antgamdia merged commit 0183fc9 into vmware-tanzu:master Nov 4, 2020
@antgamdia antgamdia deleted the faviconMismatchFix branch November 4, 2020 15:36
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

Successfully merging this pull request may close these issues.

None yet

2 participants