If titles are important, pages should have a title banner or heading in the page itself, and not rely on users looking at the title up at the top of the browser window.
Maybe I'm not the typical user, but I personally find page titles extremely useful when using a back button. I get annoyed when I expand the back history and just see the site name for every entry. I've also noticed a trend in browsers like Chrome that use the title as an autocomplete hint in the address bar.
Also, beyond the SEO importance highlighted by the article, if you have multiple pages indexed in a search engine, it makes it much easier for an actual user to locate a particular page of interest. As a side note, I am actually more inclined to click a search result if the title looks like it was made for me, seems to match my intent, and looks like it was not just constructed for a search engine.
And in that context I also do not agree with the suggestion in the article. Displaying only on which page you are currently will be good enough much of the time but not always. Finding a (short!) way of denoting which website you are on seems sensible to me.
Now, honestly, this doesn’t apply to the page he mentions. You could indeed cut the BBC out. “Doctor Who” becomes the important information – but that identifier should definitely be preserved. Now, having titles like “Contact” or “<Title of Article>” – that would be a bad idea.
Most people I know just remember the URL or search for the page on Google if they want it again. Googling "Doctor Who" gives the BBC site as the first result.
It really couldn't be any shittier, and only a handful of people have ever implemented anything else. It also makes it impossible to usefully cache the whole page, which is just deadly for an API.
At minimum, your page numbers should be in the same reverse order that your content is. A better implementation is to have the pages represent fixed periods of time (hours/days/weeks/months/years).
http://www.dehora.net/journal/2008/07/20/efficient-api-pagin... is the only clear elucidation of this insanity I've seen.
It's better to not expose paging in the UI than to cock it up like everyone else. Having real links to "Page 2" in Twitter's timeline would be a terrible idea -- it would be anything but a permalink, as the content would change completely 20 tweets later.
So this has its applications and calling it a “loathsome […] UI sin” is more than a bit over the top.
(It's Yahoo. This is the single most-used piece of UI on Yahoo other than the front page. Do you really think we don't do it because we're lazy? We never got around to persisting the username in 14 years of endlessly recoding the login page?)
But there's another reason not to have it persist depending on the style guide for forms on your site (you are using a style guide, correct?). The style guide may say that incorrect fields be called out as incorrect, using an icon or a red border or whatever; the correct fields are not called out and do persist their values, so you only need to change the incorrect ones. With a login form, the entire form is invalid, so do you persist the values in all the fields but indicate that they're all bad? This may require a change in your site's style guide, to acknowledge the existent of entire forms that could have invalid data and are not in an editable state, but it's does require not just blindly persisting the login name.
Is that necessary with a properly structured form?
2) ...that dotted line is so ugly...but fine
5) html maxlength attribute? maybe this is too web 1.0 for some people
8) ...ut if you do not prefix your title with, por ejemplo, BBC then BBC bookmarks will be mixed with others. At least this way when sorted alphabetically bookmarks from the same domain will be grouped together and even sorted correctly amongst themselves.
Colours have very different meanings depending on where the culture. The go-to example is how red is percieved in the U.S. (danger/bad) versus China (happiness/luck).
With regards to website names in titles, URLs aren't displayed in some history lists. It's also important to remember the sizable chunk of the population that Googles everything and has no idea how to read a URL.
