In Bug 1174132 we changed behavior to use the title in the <title> tag instead of the og:title. We would like to switch this back and prefer og:title – while we might encounter some sites with poorly done titles, the same is true of the title tag itself, and generally og:title is higher quality. Because the change happened in PageMetadata.jsm (https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/PageMetadata.jsm#182) I would actually propose that module should *return* og:title as a separate attribute from title, so that the display decision can be made late, and it doesn't affect any existing code.
Priority: -- → P3
See Also: → bug 1174132
og:title should already be in the result, all meta tags are stored: https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/PageMetadata.jsm#110 We should only be doing touchups where it makes sense, though some og tags are still overwriting (e.g. description).
hmm, but the title handling is a bit weird. +1 on cleanup.
I'm proposing we should have access to both result.title (the <title>), and perhaps result.ogTitle (the og:title), or maybe result.og.title. In general it looks like the order of tags in the <head> defines the data that is returned, which seems unreliable. For instance the data typically put into <meta name="description"> tends to be intended for SEO, while <meta name="og:description"> is intended for display. (And I don't know what <meta name="DC.Description"> is used for, but it might also be relevant.)
(In reply to Ian Bicking (:ianb) from comment #3) > I'm proposing we should have access to both result.title (the <title>), and > perhaps result.ogTitle (the og:title), or maybe result.og.title. In general > it looks like the order of tags in the <head> defines the data that is > returned, which seems unreliable. yes, that is what I meant in comment 2. IIRC intention was to ensure there was a title if one or the other didn't exist, but it doesn't look quite right.
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.