What?
After #2192, authors can specify a custom asset to be used as the favicon in browsers. Currently, this works by overriding the default asset at runtime. A better method would be to replace the default favicon file with the custom asset file as part of the build process.
What? After #2192, authors can specify a custom asset to be used as the favicon in browsers. Currently, this works by overriding the default asset at runtime. A better method would be to replace the default favicon file with the custom asset file as part of the build process.
Why? See discussion on #2192.