If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Changing the top level's windows name is confusing



Fennec Graveyard
9 years ago
4 years ago


(Reporter: dougt, Assigned: mfinkle)



Windows Mobile 6 Professional



(1 attachment)



9 years ago
When a page changes the window.title, our application's window reflects this change by setting its title to :

<window.title> - Fennec

I think we should stop updating the application's window's title for the following reasons:

1) most window.titles are long resulting in not being able to see "Fennec" while using fennec.

2) switching back to Fennec, the user must remember what the last page they were visiting, or remember what the Fennec icon is.  For example, if you visit DIGG.com, when switching back to Fennec using the HTC Task switcher, you see:

[FENNEC ICON] All News, Videos, ...

on a google search result page, you'd see:

[FENNEC ICON] foopy - Google Se...

3) it is somewhat redundant.  The URL bar already shows what window.title is.  So, if you are at the top of a page, you see two strings that both are window.title.

perhaps we can just switch it to "Fennec - title"


9 years ago
Keywords: uiwanted

Comment 2

9 years ago
sure.  i guess, i would question, what is the value of " - title".
If you're panned away such that you can't see the address bar, it gives you the title.  The follow up question would be, what does it hurt?  Or probably even better, what can we do with the space that's more useful?
The first word (if there are multiple) should definitely be "Fennec."

I think that the making the window-title-be-the-title behaviour is mostly there because, on the desktop, you might have many windows open with different pages loaded.  This makes less sense in a multi-tab world;  even less so when you don't have multiple windows, as on mobile.  I'd be pretty happy to drop the page title and just go with Fennec.  Less visual clutter.

Comment 5

8 years ago
gavin/mfinkle, what has to be done here?  Can we just drop off some properties on browser.xul?
(In reply to comment #5)
> gavin/mfinkle, what has to be done here?  Can we just drop off some properties
> on browser.xul?

patch coming up
Created attachment 386063 [details] [diff] [review]

Patch removes the updating of the chrome window title. Removes unneeded DTD entity. Removes unneeded attributes on the <window> element.
Assignee: doug.turner → mark.finkle
Attachment #386063 - Flags: review?(gavin.sharp)


8 years ago
tracking-fennec: --- → ?
Attachment #386063 - Flags: review?(gavin.sharp) → review+
Last Resolved: 8 years ago
Resolution: --- → FIXED
tracking-fennec: ? → ---
You need to log in before you can comment on or make changes to this bug.