• Please note that this section is for questions regarding the forum itself - it is not for fan game-related questions. If you have a question about a fan game, ask in the appropriate thread.

  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Our weekly protagonist poll is now up! Vote for your favorite Trading Card Game 2 protagonist in the poll by clicking here.
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.
    Register

What's up with CSS?

Alice

(>^.(>0.0)>
    • 3,077
    Posts
    16
    Years
    I just taught myself enough CSS to create a simple showcase for my new hack, so nothing very complex, but when I save my edits, PC writes all sorts of random extra code that I didn't put in, messing up my backgrounds, adding weird lines and borders all over the place, and making it simply impossible to use. I mean, what am I supposed to do if it automatically writes things I don't want into my post when I post it? I can delete the stuff added, but it will always come right back. I've noticed the same thing happening with quoting at times too, but not all that often. I finally got my thread looking right, but now if I make any changes whatsoever, even just changing text or swapping out an image for an identically-sized one all sorts of random crap gets added to it. How do I stop it from doing that, and is it a problem with PC, or CSS, or me?
     
    I assume it may be from PC since that happens to me sometimes too. Dunno what it is though.
     
    Not sure how to post the code in a raw form on here, but I think the linebreaks were actually the problem anyway. Took them all out and used padding instead, and it seems to be working alright so far.
     
    QuilavaKing said:
    Not sure how to post the code in a raw form on here, but I think the linebreaks were actually the problem anyway. Took them all out and used padding instead, and it seems to be working alright so far.
    Click to expand...

    For future reference, [NOPARSE][/NOPARSE] is what you're looking for :)
     
    You must log in or register to reply here.
    Back
    Top