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

span.count

My only gripe with 0.1.37 is the change with span.count. What's the reasoning behind leaving the parentheses outside the span? For me the point of a count class was to make it visually secondary to the actual rating... I think having the parenthesis outside the span is actually more distracting that not having a span.count at all. It looks like the rating in group status in show=anime has it the old way; compare that with the mylist anime ratings and I prefer the former.

If I'm in the minority, then :: shrug ::. Regardless, Kickass update. Grats to whoever did all that work :).

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)