Use favicon full path
What does this MR do?
Use favicon full path so we don't trip when name is content hashed
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
(that little flicker isn't consistent, must be because the dev favicon is added async too :))
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together