-
Notifications
You must be signed in to change notification settings - Fork 868
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
add welcome page favicon #543
Conversation
@@ -75,6 +75,7 @@ void CustomizeWebUIHTMLSource(const std::string &name, content::WebUIDataSource* | |||
} | |||
}, { | |||
std::string("welcome"), { | |||
{ "ecaefa14dcf65df518730a336430727e.ico", IDR_BRAVE_WELCOME_FAVICON }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a question here - why are we using these hashes for filenames and not the actual readable (and permanent) name? Presumably webpack can be configured to keep them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only because file-loader
defaults file names to md5 hash. I guess this came from the boilerplate which was carried over from b-l and just lacks custom config.
webpack handles this via file-loader options
by declaring name name: '[path][name].[ext]'
, but this seems to require changing all previous hashed files to their original names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
closes brave/brave-browser#584