Hey Bevan - great work on this module.
Can you clarify this:
It needs some work so that it doesn't operate on operations in admin tables.
What is an example of an operation in an admin table?
I'm also thinking that perhaps this same idea could be executed as patches to the individual modules, though that obviously takes a lot longer it has the benefit of providing more precise targetting. It would also have the benefit of working for the 10% of the internet that doesn't have js enabled.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | New window links on admin-content-node.png | 104.05 KB | Bevan |
Comments
Comment #1
Bevan commentedGreat question. I attached a screenshot that shows what I mean. "admin tables" is probalby not a good term.
Definitely. That would probably be the way such a change would need to be implemented in core.
Not if we want to be XHTML-compliant. The
target=""attribute is invalid XHTML. Without javascript I don't believe there is anyway to output valid XHTML and have links open in new windows.Comment #2
gregglesInteresting.
Well...now we have the ultimate smackdown: degradable usability vs. web standards.
Comment #3
Bevan commentedI don't think it's a significant issue, since users without js are clearly a minority, and everything still works without js, just in a slightly less-usable way – the current way.
Where did you get 10% from? That doesn't seem right to me. I suspect that includes bot traffic, which probably makes up for about 10% of all internet traffic anyway, and needn't be considered for this issue.
Comment #4
Bevan commentedComment #5
Bevan commentedComment #6
greggleshttp://www.google.com/search?q=percent%20of%20users%20javascript%20disabled shows a lot of answers. Seems like 10% might be high depending on whose stats we want to use.