Justin Lebar (not reading bugmail) Reporter
	Description • 14 years ago

(I have difficulty imagining this isn't already filed, but I can't seem to find it.)

I have http://docs.python.org/library/index.html in my awesomebar history.  When I type that URL, Firefox displays

  "The Python Standard Library -- Python v2.6.5 documentation"

as the title.  But the page's actual title reflects the current version of Python:

  "The Python Standard Library -- Python v2.7.1 documentation"

When I visit a page and its title is different from what Places has stored, Places should update its stored title.

	Shawn Wilsher :sdwilsh
	Comment 1 • 14 years ago

Did you bookmark this url?

	Justin Lebar (not reading bugmail) Reporter
	Comment 2 • 14 years ago

Aha, yes.  Didn't notice that.

	Shawn Wilsher :sdwilsh
	Comment 3 • 14 years ago

(In reply to comment #2)
> Aha, yes.  Didn't notice that.
Then this is likely the intended behavior.  We'll always show the bookmark title over the page title because the bookmark title is user-set.

	Justin Lebar (not reading bugmail) Reporter
	Comment 4 • 14 years ago

The bookmark title is user-settable, but in this case, it was not user-set.  I imagine that's the common case.

Perhaps Places should be aware of whether the title was *actually* set by the user.

	Marco Bonardo [:mak]
	Comment 5 • 14 years ago

I think we should change all of our titles management in a next schema, since it's insane.  Btw, it's hard to figure out if the user changed the title or not, since the API calls are the same, the backend API just knows someone asked to add a bookmark with a certain title, we could guess that if the bookmark and history titles are the same user didn't change it, at last.

	Marco Bonardo [:mak]
	Comment 6 • 14 years ago

let's transform the bug, I can't find the dupe for now, even if I recall previous bugs about this, will dupe in future in case.

	Brian Smith (:briansmith, :bsmith, use NEEDINFO?)
	Comment 7 • 13 years ago

Use case: I bookmark a bug. Then the bug's summary changes. All my email for this bug has the new summary in the subject, but the awesomebar always retains the old summary. This happens to me all the time.

	Justin Lebar (not reading bugmail) Reporter
	Comment 9 • 13 years ago

As I said in bug 723972, this bug is much more visible with the new-tab page.

	Elbart
	Comment 11 • 10 years ago

Any news?