Make WordPress Core

Opened 9 years ago

Closed 9 years ago

#4140 closed defect (bug) (fixed)

Tags UI be UGLY

Reported by: andy Owned by:
Milestone: 2.2 Priority: normal
Severity: normal Version: 2.2
Component: Administration Keywords: has-patch
Focuses: Cc:


[5110] introduces a hella ugly tags interface. Clean it up.

Attachments (3)

tags.diff (1.4 KB) - added by andy 9 years ago.
Make you pretty.
tags.2.diff (1.4 KB) - added by andy 9 years ago.
This time with new wording.
4140.diff (366 bytes) - added by Sewar 9 years ago.

Download all attachments as: .zip

Change History (12)

9 years ago

Make you pretty.

#1 @andy
9 years ago

Nice fix but... Hmm, now the text doesn't line-wrap when the window is narrow.

9 years ago

This time with new wording.

#2 @andy
9 years ago

Second try changes the wording to make it shorter and more like the Categories explanation. Do we really need to explain what tags are in the UI? I don't think we do. We don't explain categories. New wording in tags.2.diff:

Tags (separate multiple tags with commas: cats, pet food, dogs)

#3 @markjaquith
9 years ago

  • Milestone changed from 2.4 to 2.2
  • Version set to 2.2

I don't think we should explain tags, and I don't think we should be using Bubblespeak tags as examples. :-)

Can we move away from underscores in class/ID names? They're not compatible with 100% of browsers, so going forward we should probably be sticking to dashes as much as we can.

As a bigger issue with tags, I think we should be blanking the input box after saving tags, and use Flickr-style for showing existing tags and deleting existing tags.

Add tags (separate multiple tags with commas):

Existing Tags:
[x] San Francisco
[x] Parties
[x] Venture Capital
[x] Everything 2.0

Right now, you have to use your mouse to select a tag (and its leading or trailing comma) and delete it... yech...

As you can tell, I'm a big fan of Flickr's tagging interface.

Check out this:


(obviously this was for Categories, so the hierarchical stuff doesn't make sense)

#4 @rob1n
9 years ago

We can do that Flickr interface stuff for 2.3. Personally I think it's a great idea -- Flickr has some pretty good UI that we can learn from. I believe there was a ticket integrating something else from the Flickr interface somewhere along the line.

For now, IMO we should just focus on getting that input box un-screwed up for 2.2.

#5 @rob1n
9 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [5254]) Tidy up the tags interface. Props andy. fixes #4140

#6 @markjaquith
9 years ago

(In [5257]) CSS IDs should avoid using underscores for compat with older browers. See http://tinyurl.com/2s99u6 addresses #4140

#7 @Sewar
9 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Let's update RTL CSS also.

9 years ago


#8 @Sewar
9 years ago

  • Keywords has-patch added

#9 @rob1n
9 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

(In [5264]) Add RTL css for #tagdiv. Props Sewar. fixes #4140

Note: See TracTickets for help on using tickets.