Closed
Bug 1479722
Opened 3 years ago
Closed 3 years ago
setCharsetForURI should use history.update
Categories
(Toolkit :: Places, enhancement, P2)
Toolkit
Places
Tracking
()
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: mak, Assigned: standard8)
References
Details
(Whiteboard: [fxsearch])
Attachments
(2 files)
this is one of the remaining uses of the page annotations API
| Assignee | ||
Updated•3 years ago
|
Assignee: nobody → standard8
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•3 years ago
|
||
MozReview-Commit-ID: HeO3Mm5Dibo
| Assignee | ||
Comment 2•3 years ago
|
||
Depends on D2582
| Assignee | ||
Comment 3•3 years ago
|
||
Try push is here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=ce2d671457b86b0fe024b3b003e774888062e3c7
Comment 4•3 years ago
|
||
Comment on attachment 8996468 [details] Bug 1479722 - Rework PlacesUtils.setCharsetForURI to PlacesUIUtils.setCharsetForPage and avoid main thread sync io. Marco Bonardo [::mak] has approved the revision. https://phabricator.services.mozilla.com/D2582
Attachment #8996468 -
Flags: review+
Comment 5•3 years ago
|
||
Comment on attachment 8996470 [details] Bug 1479722 - Remove nsIAnnotationService::setPageAnnotation and removePageAnnotation. Marco Bonardo [::mak] has approved the revision. https://phabricator.services.mozilla.com/D2583
Attachment #8996470 -
Flags: review+
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/26c498b422eb Rework PlacesUtils.setCharsetForURI to PlacesUIUtils.setCharsetForPage and avoid main thread sync io. r=mak
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fde7e80c27a7 Remove nsIAnnotationService::setPageAnnotation and removePageAnnotation. r=mak
Comment 8•3 years ago
|
||
Is the charset information still needed in the history? The only remaining user is keyword bookmarks. How about adding charset to moz_keywords instead of annotations?
| Reporter | ||
Comment 9•3 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #8) > Is the charset information still needed in the history? The only remaining > user is keyword bookmarks. How about adding charset to moz_keywords instead > of annotations? It's indeed an interesting suggestion that I thought about time ago too, once we have an abstraction we can do anything. There are 2 problems there: 1. we don't know if the user will add a keyword to a bookmark at a later time, thus we have to store the charset regardless 2. the user can still force a charset for a page through the main menubar (though I'm not sure if that info is still used properly) I think we should see if bug 648398 goes anywhere, anyway it should not be a big deal to keep things as they are for a while.
Comment 10•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/26c498b422eb https://hg.mozilla.org/mozilla-central/rev/fde7e80c27a7
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•