#8903 closed defect (bug) (duplicate)
wp_tag_cloud invasive styling
| Reported by: | Appletalk | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Template | Version: | 2.7 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | Focuses: |
Description
Follow this guidelines
http://24ways.org/2006/marking-up-a-tag-cloud
or others if you like, but having the font-size in the markup stinks :(
Change History (4)
#1
@
18 years ago
- Keywords needs-patch added
- Milestone 2.7.1 → 2.9
- Priority high → normal
- Version → 2.7
#2
@
17 years ago
- add new function wp_generate_tag_cloud_array() that takes care of data only
- that data should handle the absolute weight (min-max) as well as relative (1-5)
- use the new function on your own will
- update wp_genereate_tag_cloud() to use the new function as well.
going that route will seperate the concerns and refactor wp_generate_tag_cloud() a bit.
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
So.. Going by those guidelines, Each item shouldn't have a size specified, Instead, It should be on a pre-determined ranking of 1-5 basically (or whatever scale chosen)
I do agree.. Having the size in the html stinks.. but it doesnt feel right to me to remove functionality like that.. Esp. when for backwards compat theres per-theme values to take into consideration.
Settings to 2.9 as theres no patch, Generally wouldn't make it into a .point release anyway.