251588 2023-02-02 08:01:36 -0800 [GTK] Don't enable favicon database by default 2023-02-06 03:49:01 -0800 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build PC Linux RESOLVED FIXED P2 Normal --- 210100 1 mcatanzaro cgarcia bugs-noreply cgarcia mcatanzaro oldest_to_newest 1930472 0 mcatanzaro 2023-02-02 08:01:36 -0800 I asked Carlos Garcia to enable WebKitFaviconDatabase by default in the new API, since web browsers want favicons. But I think this was a mistake, because WebKitFaviconDatabase does not do anything useful unless your application has code to use it. 1930845 1 cgarcia 2023-02-03 06:12:03 -0800 I've thought about this, because favicon database now can be null, which maybe it's not the best approach either. You might want to disable favicon loads, but still get favicons from the database, for anything in the browser UI (bookmarks, etc.). So, I can think of different options here: 1.- Leave things as they are but simply change the default value to disabled. 2.- Disable favicon loads per WebView, for example using a new setting, but favicon database can still be used to query favicons. 3.- Disable favicon loads per request, by adding a new signal that would expose IconLoadingClient::getLoadDecisionForIcon(). In this case, favicons database can always be used too. The signal is similar to accept-certificate, where you are supposed to just return TRUE or FALSE. I think we can keep it synchronous too. In case of 2 and 3 if the database is not used by the app and the setting disabled or signal unhandled or returning FALSE, the database is not even created. 1930853 2 mcatanzaro 2023-02-03 06:46:57 -0800 I'd prefer 1. > You might want to disable favicon loads, but still get favicons from the database, for anything in the browser UI (bookmarks, etc.). Why? 1931087 3 cgarcia 2023-02-03 23:07:46 -0800 (In reply to Michael Catanzaro from comment #2) > I'd prefer 1. > > > You might want to disable favicon loads, but still get favicons from the database, for anything in the browser UI (bookmarks, etc.). > > Why? For anything in the browser UI like bookmarks, history, etc. But I guess in the end apps either want favicons for everything or nothing, so maybe 1. is indeed the simplest solution. 1931321 4 cgarcia 2023-02-06 01:53:44 -0800 Pull request: https://github.com/WebKit/WebKit/pull/9678 1931339 5 ews-feeder 2023-02-06 03:48:58 -0800 Committed 259888@main (ac3878ed7421): <https://commits.webkit.org/259888@main> Reviewed commits have been landed. Closing PR #9678 and removing active labels.