I knew what he meant immediately I read the entry, as it's one of my bigger bugbears about default behaviour, and one of the first things I taught myself to fix when learning S2 (you helped me with it IIRC).
@OP: I'm taking on the role of DW documentation lead writer, and I actually agree with you re the actual problem, that it's not clear, and that it needs fixing, and should be available as an option.
However, a) I've been ill, and therefore unable to pay attention to support and this comm as much as I like to and b) regardless of my opinion on an issue, if anyone wanting help went arround attacking volunteers and calling them liars when they say "I'm not aware of this happening elsewhere", they'll get very short shrift from me, regardless of how I feel about the issue under discussion.
There is a fix, it's fairly easy, but currently requires setting up your own layer. At some point, when I'm well enough, I'll be turning the work I've already done to get it working on my journal into a layout available to all, but this is a site still in the beta stage of development.
@ninety. This is one of those instances where accessiblity and usability can clash. The way we deal with page titles is very bad for both usability and accessibility, the ideal is if someone has multiple tabs from the same journal open, each should be distinctly indentifiable within the tab display (Nielsen wrote some very good stuff on this for Alertbox a few years back).
Hopefully, my health is recovering, so I'll get some coding done to make my floatable layout ready enough for others to test it. It has many many many options within it that I suspect the OP might quite appreciate. Hopefully he'll learn some manners if he comes back.
no subject
@OP: I'm taking on the role of DW documentation lead writer, and I actually agree with you re the actual problem, that it's not clear, and that it needs fixing, and should be available as an option.
However, a) I've been ill, and therefore unable to pay attention to support and this comm as much as I like to and b) regardless of my opinion on an issue, if anyone wanting help went arround attacking volunteers and calling them liars when they say "I'm not aware of this happening elsewhere", they'll get very short shrift from me, regardless of how I feel about the issue under discussion.
There is a fix, it's fairly easy, but currently requires setting up your own layer. At some point, when I'm well enough, I'll be turning the work I've already done to get it working on my journal into a layout available to all, but this is a site still in the beta stage of development.
My post with my initial code is here: Anyone that's read my ramblings online for awhile knows that I take usability and search presence fairly seriously. There's no point in writing something for a general audience if people that are interested can't find what you've written. Dreamwidth's default settings for page TITLE tags were, well, a bit weird, and broke basic usability and SEO rules. So I've been hacking.
@ninety. This is one of those instances where accessiblity and usability can clash. The way we deal with page titles is very bad for both usability and accessibility, the ideal is if someone has multiple tabs from the same journal open, each should be distinctly indentifiable within the tab display (Nielsen wrote some very good stuff on this for Alertbox a few years back).
Hopefully, my health is recovering, so I'll get some coding done to make my floatable layout ready enough for others to test it. It has many many many options within it that I suspect the OP might quite appreciate. Hopefully he'll learn some manners if he comes back.