| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Comments:
<0> Zoffix: look away
<1> :)
<2> p34r: Dude, make with the goods.
<0> ShortWave: ?
<2> p34r: You said the design was beautiful, i wanna see.
<0> ShortWave: yeah but im like on a contract and im backed by investors on this website i cant really release it
<0> Zoffix: i wasnt even suppose to show it to zoffix haha
<1> heh
<2> p34r: Did you sign an NDA?
<3> Heh.
<0> http://pastie.caboo.se/34573
<0> firefox wont even make the link clickable, nor the div
<4> riczho: back to the actual problem I'm having in FF. on that design page, do you see how the large tree background shifts up in FF? Doesn't do it on any of the other pages
<0> but opera and ie follow accordingly
<1> p34r: dude! I gave you two damn pastebins, with __HIGHLIGHTED__ instructions on how to paste properly, and you still pasting to crap-bin
<1> p34r: your paste is useless to us
<1> ]irc url @ p34r
<5> p34r, Provide a live link: http://dorward.me.uk/irc/#context
<3> Nautilus: overflow: auto; on #content_wrapper
<4> what is the idea behind that?
<4> riczho: ah, reading on w3
<4> hm, I'm not going out of the content box
<2> Nautilus: This is why you need the web developer plugin
<4> oh i have it
<4> in FF and IE
<2> Nautilus: coolio.
<4> it doesnt show anything about the background image though
<4> and the same code is working on the other 4 pages written so far
<2> Nautilus: If I do "CSS -> Disable Inline styles", the tree lines up correctly.
<4> ShortWave: oh, indeed it does
<4> what a pain
<2> Nautilus: So you know, that narrows it down for you.
<4> not really
<2> Nautilus: Also on FF, that picture on the right hand side overlaps the text on the Art page.
<4> which inline style? why on one of 5 pages and only in FF?
<4> yep, another FF problem.
<3> Nooo!! minibot!!!
<4> that pic is fine in IE6
<3> Nautilus: float: right on the right column [ugly cl*** name deleted]
<3> Silly user.
<3> Whoops. Wrong channel.
<4> float right sounds apropos
<4> riczho: yep, that fixed the right-hand pic, ty
<6> hmm, any help would be apprecitated here http://dev3.iwire.com.au/demo.htm
<6> the images all load fine and looks good in firefox
<6> but in ie they lag
<6> and looks like a acordian going donw
<6> down*
<4> hor: so what could be the problem with inline styles?
<6> no what im saying
<4> err...
<4> ShortWave: so what could be the problem with inline styles?
<4> oh lemme validate it
<1> Nautilus: you are probably defining some inline styles on that page... try your thing with !important, or look at the source and see what your are setting there inline
<1> ]css !important @ Nautilus
<5> Nautilus, css !important: http://w3.org/TR/CSS21/cascade.html#important-rules
<4> I'm setting styles inline ;)
<4> validation on the design page OK
<7> ugh where else in cpanel are logs stored?
<4> naming == yawn
<3> bad naming == shriek!
<4> i could eliminate the names by using tables ;)
<8> Nautilus: stop right there
<3> Really- if you can't even justify it, you have to question the correctness of your approach.
<4> justify... what?
<4> names??
<3> Justify names such as navbar_left, etc.
<3> As opposed to names that just describe the content and will always make sense.
<4> thats a very descriptive name
<4> content = the left half of the nav bar
<3> I sense that you haven't ever designed a website that's survived more than one version.
<4> riczho: that may be true, but again, yawn.
<3> Nautilus: That doesn't only describe what the content is, it describes where it is.
<4> on the left, yep. it does not work if it was on the right.
<3> Nautilus: If you decide to use a vertical menu, for example, then you'll have to change it.
<4> sure
<3> So it's stupid to make yourself do it.
<4> if I'm doing THAT much work (complete redesign), then renaming is little consequence
<3> The point is that you won't have to modify the markup largely to change the design.
<4> my point is the markup doesn't work in the first place
<4> s/markup/coding/
<3> That's because of your bad naming.
<4> lol
<4> the background moves because of my naming?
<3> That's an unrelated issue.
<4> it's the issue i asked about
<3> But your page is harder to work with and is more rigid because of your naming.
<3> One of the cases against tables for mark is that it's purely presentational markup.
<3> The right/left/center stuff is bad in the same way.
<3> Nautilus: We fixed the issue- overflow: auto; remember?
<4> haven't tried that yet... my q was why, when nothing overflows? (unless I misunderstand overflow)
<4> The behavior of the 'auto' value is UA-dependent, but should cause a scrolling mechanism to be provided for overflowing boxes.
<4> YUK!!
<3> Float containment.
<4> the BG isn't a float
<3> Considering that it's caused by inline styles, I'm probably going to blame the float: right; on the name thingy for that.
<4> that's a div of fixed size, no contents overflow it, yet the background moves?
<4> I have other pages with less and more content (vertically)
<4> they work
<3> Did you see what I said about the float on the page?
<4> float right on a name thingy, bear with me... where do ya mean?
<4> ohhh, on his name? Keiths?
<3> Yeah.
<4> ah, thanks, an actual thing to think about, that
<4> is span itself bad, did I do that wrong?
<3> Well, floating a span is kinda pointless.
<3> (Since float implies block)
<4> combined with experiences during development, your blame may be coorrect.
<4> how would you do that given a cl*** for the paragraph that is "text-align: justify;" and I just want to put his name on the right like a sig?
<3> The float: right; thing, probably.
<3> A div with text-align: right; would probably have worked too.
<4> w/o a span?
<3> Either way, I need a block element.
<4> well yea a whole div for itself would work, but man.
<4> without going to a special div (which you'd hate 'cause the name would appropriately include "right"), how can apply a right to just those 2 words, after the _br_
<3> Can't.
<4> ok, so I'll test a statement_signature {} tomorrow. I think you may have id'd the issue, and tyvm!!!
<4> (i guess that name doesnt need position info after all) ;^)
<4> all sigs have common placement
<3> No problem- and better name :)
<4> riczho: thanks again for bearing with me. If a dedicated div makes things work better, that's the goal.
<4> riczho: man, thought ya had it. took out the whole section with br, span and his name (locally), and no help.
<3> Darn.
<4> that's one word for it ;)
<3> OK, I blame the clear now.
<3> For some unknown reason.
<4> the Opera clear?
<3> The one on the random <br>
<4> hm, local copy has the br commented out. should be posted that way
<4> commented that out about 2 hours ago
<3> Or maybe not...
<3> Hm.
<3> * { clear: none!important; } "fixes" it, so I blame a clear some where.
<3> **somewhere
<3> Wait... disabling inline styles doesn't fix it!
<3> Somebody said that and I was paying attention to those...
<4> a global clear none.. isn't that the default??
<3> !important overrides everything else.
<3> Well, not *everything* else.
<3> But everything else that you had.
<4> they should have spelled css s.p.a.g.e.g.e.t.t.i
<4> s.p.a.g.e.t.t.i
<3> OK, strategy two: delete stuff until it's fixed.
<4> nod, there is always that. take everything out and start over
<4> with tables.
<4> lol
<9> uhg
<9> if you people understood what your websites were doing you wouldn't **** at css
<9> and i'll give you the benefit of the doubt that it is "hard"
Return to
#css
or
Go to some related
logs:
#debian
#mysql
mysql modify collum
mencoder g3p
#osdev
#debian
#perl
dapper cs330
task-bootstrap ipk
#qemu
|
|