kunzite (kunzite1) wrote in component_help,

  • Mood:

css issues

you will not post and say "my layout is fucked! please help!"
you will not post your layer code in your entry.
you will not bitch and complain because you don't know what you're doing.

you will read the documentation.
you will make your layer viewable and post the layerid.
you will specify which parts are hosed, why they're hosed, and what their unhosed states look like.

you will not comment and say "yeah! my layout's fucked too!"
you will not comment and say "yeah. it's cuz of the new css stuffs."

so. how's that?

i'm annoyed too. but my layouts are happy due to not hacking 'em up much.
however, there are some new toys that i'd like to play with, but i'm not doing squat until they iron out all the bugs that were made because they didn't have people test the existing layouts to see if they were happy.
they just had the people come up with hacks to see if anything got through.
they didn't check to make sure that their stock s1 code still passed.
or that their stock s2 code still passed.
or that other layouts dependent upon @import rules still worked. they died because they disallowed the @import rule.

also. if something is fucked with your css, check around where Page::print_custom_head() is shoved into your html source code (the stuff that happens when you load a journal page and do the view -> source thing. not your layer source). also get the link to your stylesheet and read that. it might also have that suspect css garbage.

to go with the above list: you will post the exact error that the css script gives you.

oh yeah. fuck lj-cuts because i rule around here. yeah, i'm on my high horse, but i hate this shit just as much as the rest of you.
Tags: admin: kunzite1, user: kunzite1

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened