Bug 78697
| Summary: | Remove the need to have a database for getting the favicon | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | andy.shaw |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Enhancement | CC: | ap, beidson |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
andy.shaw
Remove the need to have a database for getting the favicon as in some cases it is not possible for a browser to write to the local system but it would still want to show the favicons. So it would be good if this could still be running without having a database to write to.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
The database can be in-memory, why is this an issue?
andy.shaw
If it can be in-memory then I missed that and that would be sufficient, can you point me to where I can see that so I can look at it further?
Brady Eidson
I'm not sure there's currently a way to enable an in-memory icon database, but it should be possible to add a hook to tell sqlite to open an in-memory database instead of opening one on disk.
It might be as simple as setting a special in-memory URL for the database path preference, I'm not sure if that's possible as I forget the semantics of SQLite in-memory databases.
andy.shaw
I am aware of the :memory: approach, but from what I could see it would validate the path on the system, and have its own filename set so it wasn't so straightforward to specify it should use :memory:. Though I would welcome that as being the solution, it would be sufficient enough
Brady Eidson
What port are you working on, btw?
I'm curious about what your situation is where you want in-memory icons.
andy.shaw
I am actually working with QtWebKit, but my role is actually in the Digia Qt Commercial support team and the request came via something that came up there