People get lost and confused by clicking on the "+foo" links that label inclusions in multi-edit.
Just make them regular unlinked text.
It is handy sometimes, so maybe make the page icon appear when hovering over these labels, so that you can click on the icon to go to the card.
coded: bba8493
weird, they're still green, and underline when oyu hover, but nothing happens when you click.
--John Abbe.....Sat Feb 19 17:20:15 -0800 2011
If you keep working on this, I guess remember to update the coded field up top.
--John Abbe.....Sat Feb 19 17:20:44 -0800 2011
I just switched them to unlinked anchors (still "a" tags, no href). My rationale was that was the easiest way to solve the issue without messing up anyone's styling anywhere.
I kinda forgot to review the solution here before doing it. Do you think it's worth taking away the a tag? Doing the icon thing makes this a bigger deal because it's something that would need design effort, browser testing, warning folks about interface change. Not saying we can't do it, but it probably drops off 1.5.3 if that's important.
I'm a weak vote for moving forward as is and moving the icon thing to an Idea card.
--Ethan McCutchen.....Sat Feb 19 20:24:15 -0800 2011
also thanks for making the commit field!
--Ethan McCutchen.....Sat Feb 19 20:24:55 -0800 2011
I'm a vote in favor of removing the a tag, or at least restyling it so it doesn't look like a link. People who were tempted to click on it before still will, and then they'll still be confused (though at least not lost as well).
I'm okay if we don't add page icon to multi-edit labels now, I don't think I clicked those links that often, and if I find that I want it badly I'll just bug you about it. :-)
--John Abbe.....Sat Feb 19 20:39:57 -0800 2011
what if we went with the current improvement for 1.5.3 and then restyled it altogether in some other release that has a lot more css consequences. I know some have styled those things (eg fortzed), and if I'm going to have to go digging around in *css cards, I'd rather being fixing lots of things at once.
--Ethan McCutchen.....Sat Feb 19 20:58:30 -0800 2011
I can live with that. Slightly embarrassing as is, but can't say it isn't a step forward.
Should I ticket that one thing, or add it to a new ticket that bundles a bunch of these? (I'm not seeing one that it would fit in, but if you do, go for it.)
--John Abbe.....Sat Feb 19 22:35:18 -0800 2011
Happily, I'm not embarassed about this one. I betcha any confusion will be minimal.
I'd say lets' hang this and other minor styling issues onto support skins -- that release will be the one to mess with folks' css. My current thinking is that most of the biggest interface changes (including and especially look and feel stuff) should be on the actual Wagn 2.0 release.
--Ethan McCutchen.....Mon Mar 07 17:17:42 -0800 2011
--John Abbe.....Tue Mar 08 00:01:26 -0800 2011