Deal with invalid URLs already in the places DB
Categories
(Application Services :: Places, defect, P2)
Tracking
(Not tracked)
People
(Reporter: markh, Unassigned)
Details
While initiated by https://github.com/servo/rust-url/issues/897, we must deal with a reality whereby a URL which was previously considered valid no longer is, and that these URLs might have already been saved in the places database. Attempting to load these rows and parse them as a URL might be assumed to work. We must, at a minimum:
-
ensure bookmarks and history query functions never fail due to a single bad URL, and also that no invalid URLs are returned. Eg, if you are requesting a bookmark tree, you should always get a result tree and that tree must never include a not-considered-invalid URL.
-
come up with a strategy for removing them? This will not be able to be done as they are found, because most read operations don't have write access to the DB.
-
ensure we don't sync them.
Description
•