AniDB talk:Markup DEV

This page exists to discuss possible changes to the AniDB.net HTML markup

Inconsistencies are bolded

missing stuff is italicized

New

tabbed_pane

<div class="tabbed_pane">
  <ul class="tabs">

<li id="{tab 1 id}"> <li id="{tab 2 id}"> <li id="{tab n id}"> </ul> <div id="{tab 1 id}_pane" class="pane"> <div id="{tab 2 id}_pane" class="pane hide"> <div id="{tab n id}_pane" class="pane hide">

</div>

wishlist mylist ep state

to allow for same styling as in mylist:

• div.mywishlist_all table td.mylist[.complete|.all_watched]
• div.mywishlist_all table td.seen[.all_watched]

up2date mylist ep state

to allow for same styling as in mylist for up2date sequels table:

div.up2date_all table.sequels td.mylist

should be split into

div.up2date_all table.sequels td.mylist.eps[.complete]
div.up2date_all table.sequels td.mylist.seen[.all_watched]

or similar

<button> submission

Can we move to using the <button> element instead of <input> for form submission? Here's the reasoning: http://particletree.com/features/rediscovering-the-button-element/

Done in 0.1.38

file quality rating

on anime page:

table.filelist td.quality.very high 

should be

table.filelist td.quality.veryhigh 

Notification popup

proposed structure of notification popup:

h1.[low|mid|high]
div.g_content.popup_all
 div.g_section.popup_notify
  h2 ("Anime" or "Group" etc.)
   ul
    li (1..n)

pending:

div.g_content.notify_all
 h1 (0..1)
 div.g_section.new_files
  h3.[low|mid|high]
  div.[anime|group|producer]
   h4
   ul
    li (1..n)

span.count

For all cases of the count class (span.count) I would like the parenthesis inside the span, so:

<td class="rating">9.33 (<span class="count">723</span>)</td>

Should be

<td class="rating">9.33 <span class="count">(723)</span></td>

Let's see if I can find them all:

• div.anime_all div.info span.rating.anime
• div.anime_all div.info span.rating.tmpanime
• div.anime_all div.info span.rating.attavg
• div.animehist_all div.animehistory td.rating
• div.animehist_all div.animehistory td.tmprating
• div.animehist_all div.animehistory td.reviews
• div.animelist_all div.animelist_list td.rating.anime
• div.animelist_all div.animelist_list td.rating.tmpanime
• div.animelist_all div.animelist_list td.rating.attavg
• div.group_all div.group_info span.rating.group
• div.group_all div.group_released td.rating.group
• div.grouplist_all div.group_list td.rating
• div.latest_all div.latest_groups td.rating.group
• div.latest_all div.latest_reviews_list td.rating.review
• div.latest_all div.latest_reviews_list td.rating.anime
• div.latest_all div.latest_reviews_list td.rating.attavg
• div.latest_all div.latest_hotanime td.rating.tmpanime
• div.mylist_all div.mylist_list td.rating.anime
• div.mylist_all div.mylist_list td.rating.attavg
• div.mywishlist_all td.rating
• div.mywishlist_all td.tmprating
• div.mywishlist_all td.revrating
• div.search_all div.search_results td.rating.anime
• div.search_all div.search_results td.rating.tmpanime
• div.search_all div.search_results td.rating.attavg

rating markup

• on the anime votes page the own votes aren't in a span, td or whatever, which makes them appear on top of the page

source: <td class="rating ep mid">7.65 (<span class="count">3</span>)</td> [7] <td><img src="http://static.anidb.net/pics/anidb_greenbarh.gif" width="122" height="5" alt="#" /></td>

Done in 0.1.37

Anime list

• table.anime_list td.rating.[vote|tmp|review] span.count

Latest Additions

• table.seq tr.[yes|no] td.[yes|no] (for VV)
  • Also noticed a bunch of [td|tr].anime.anime :x
• table.groups td.rating span.count
• div.latest_reviews_list td.vote.[ |anime|review].[high|mid|low] span.count
• div.latest_reviews_list td.rating.[anime|review] span.count
• table.hotanimes td.tmprating.[high|mid|low] span.count

rating markup:

• (td|span).rating.(anime|tmpanime|attavg|ep|group|review|my|..).(high|mid|low|hidden) span.count

Group List

• table.group_list td.rating.[high|mid|low] span.count

MyList

• table.animelist table.eplist select
  • still has pre-0.1.36 options

signup page

• text on the top should be in div.g_notebox or div.g_note
• holy crap is that a <font> tag?! :(
• "back" link on bottom should be in ul.g_actionlist

mylist compare

• selfish request: can we get an extra <div> or something wrapping the table.animelist so that the zakura style can match it's width to the regular mylist table.animelist (which has a <form> wrapped around it)? unless someone can figure out how to do it with the code that's there :x --Zak 01:07, 18 June 2007 (UTC)

Done in 0.1.36

Main page news items

I would like to see the news items be grouped separately, so instead of

<h4 /> <span.stamp /> <div>text</div> <h4 /> <span.stamp /> <div>text</div> ...

we would have

<div> <h4 /> <span.stamp /> text </div> <div> <h4 /> <span.stamp /> text </div> ...

i would like that too. i also want it to be a generic solution so it'll apply to animegroup and review comments too. g_timedentry or something --Epoximator 18:55, 16 May 2007 (UTC)

MyNotifies

• div.mynotifies_all div.list table
  • td[.name]
  • td[.new | .complete | .group | .all]
  • td[.date]

--Zak 03:36, 18 May 2007 (UTC)

My Place

• div.latest_votes li
  • span[.high | .low]
• div.latest_reviews li
  • span[.high | .low]
• div.latest_files li
  • <span.date />

--Zak 03:55, 18 May 2007 (UTC)

MyDbEntries (pages that contain Lameness)

• div.mydb_all

current situation:

all contain one that is of the classes 'text' & 'lame' the lame entries' are of the class 'lame' too the problem with that is, that by using the selector #layout-content div.mydb_all tr.lame all are affected (checked with firefox&opera)

• div.mydb_all table.mydb_animetitle
  • tr[.verified]
  • td.verified[.yes | .no]

Messages

• div.msg_all
  • ul has no class
    • li[.g_odd]

--Zeromind 01:10, 20 May 2007 (UTC)

Anime Reviews

• div.review [.approved | .unrated | .disapproved] not assigned properly (e.g. 'unrated' for a review with 22votes & rating >8) - in the text the states are correct

--Zeromind 21:33, 24 May 2007 (UTC)