Username:
Password: Forgot?
Register
-/+
Shoutbox - History
sivart0 : we could put sivquest in this arcade :D
sivart0 : Moo
Kesha : Testing out Qutebrowser, works pretty good
Kesha : An HTML5 arcade would be cool, not sure how HTML5 games are distributed these days, wonder if there's a way to collect them for an arcade system?
Sean : finally got rid of the arcade link. Took a while to find where it was, lol
sivart0 : Hmmmm
sivart0 : Mobole test
momo : hi sean, i found a new php arcade and who adapted HTML game on it
Sean : I'm much better at it than I was back then for sure
sivart0 : anybody can write one, been done to death
 
Updates 10/4 @ 1 AM
boss.
Posts: 961
Status: Offline
Group: Admin
Member: #1
Quote
  1. Removed the weird padding in forum view in chrome. (Kesh why didn't you tell me about this!!!) For some reason, the height:50px on the table cells worked in chrome but not firefox, so I never knew there was an issue in chrome in forum view.
  2. Also added this which works best in chrome, since my css worked best in firefox and I figured I'd give chrome something cool to make up for it
props
^ Top
what does god need with a starship?
Posts: 174
Status: Offline
Group: Member
Member: #98
Quote
cool
http://odsc.us/#


officially the worst jaxboard
^ Top
I take JaxBoards seriously
Posts: 890
Status: Offline
Group: Admin
Member: #5
Quote
I have no idea what you're talking about with #1

Edit: Okay, wow, there's a big difference in the size of padding in Firefox and chrome in forum view... either you didn't fix it or you messed it up even more. Even so, I never would have noticed weird padding because you have stupid huge padding everywhere lol

Edit Edit: Ok, finally my cache updated (for some reason it didn't right away??!?!?); yeah I see the error a LOT where people put a height attribute, then forget about it and use padding instead, which leads to whatever you're doing look terrible in Chrome... didn't realize JaxBoards made the same mistake too.

Chrome and Firefox render it totally differently, with Firefox rendering the height including the padding area, and Chrome doing the area after the padding (which makes more sense... why would you need to include the padding when you set that already...)

I guess this is what JaxBoards is supposed to look like? I never knew!
Edited by: Kesha , Oct 4th, 2011 @ 6:54 am
^ Top
Time Lord
Posts: 115
Status: Offline
Group: Member
Member: #77
Quote
box model sucks...

padding should be included in height and width calculation like firefox does...

usually I end up double wrapping stuff in divs to achieve the desired effect...

outer div for width+height and inner for padding.

which has it's own issues on IE.. god damn IE.

why? Have you ever tried to position two divs side by side? its impossible if you use a pixel padding measurement. if the screen gets two small the boxes overlap or push one lower than the other.
Edited by: Stephen , Oct 4th, 2011 @ 9:22 am
I broked it... Can you fix it Uncle Sean?
Fiction
^ Top
I take JaxBoards seriously
Posts: 890
Status: Offline
Group: Admin
Member: #5
Quote
show me an example
^ Top
-/+
Users Viewing This Topic