Ticket

+status
+priority
+tags
+commit
 

 

+solution

Any minor look & feel changes, mostly just via CSS:

 

 

 

plaintext pre - and then give it a class to distinguish from...

...the styling of pre in Basic?

 


it won't be a pre tag, just css for the white-space handling. might even do this before, as the recent refactor caused some weirdness, and this might actually net less interface disruption.

  --Ethan McCutchen.....Tue Mar 08 16:47:26 -0800 2011


I'm discovering that I actually used the field labels in multi-edit quite a lot, so I think my ideal solution would be to make them links again, but style them to not look like links. Figure?

  --John Abbe.....Mon Mar 21 23:48:15 -0700 2011


hmm. I think links should look like links.

  --Ethan McCutchen.....Tue May 01 03:14:02 +0000 2012


but this can ultimately vary by skin.

  --Ethan McCutchen.....Tue May 01 03:14:15 +0000 2012


Skins yes, there's still a conversation about defaults. I suppose the trick is to make the link discoverable/inviting enough for Wagneers but not inviting to mere Editors.

  --John Abbe.....Tue May 01 04:33:32 +0000 2012


Let's close this ticket and start over. The top says it all: solution without an issue.

What are the use cases we want to address? What are you wanting to get to easily that is currently hard? What don't we like? What are the issues?

Looking at the original list, I fixed the plaintext thing a while back, two other things are already tickets/ideas. so it's just this multi-edit stuff. Maybe we should start an improve multi-edit field views Idea and start gathering ideas there?

  --Ethan McCutchen.....Tue May 01 20:13:27 +0000 2012


most are done or irrelevant.

  --Ethan McCutchen.....2013-03-21 16:22:00 +0000