Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8359649
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T11:12:45+00:00 2026-06-09T11:12:45+00:00

Somewhere along the line I decided that having classes for position would be a

  • 0

Somewhere along the line I decided that having classes for position would be a good thing. So I created the following:

.prel {position: relative}
.pfix {position: fixed}
.pabs {position: absolute}

These classes are apply to thousands of little elements floating around, but they’re beginning to bug me.

The elements to which my relative position class applies, for example, all belong to about seven other classes. So I could just do this (where class1-class7 are all existing classes used for other purposes):

.class1,.class2...class7 {position: relative}

The reason for the question is this: I have this sneaking feeling that this is going to be one of those changes I make that I need to reverse out later. So I’m looking for advice as to which is the best way forward. Does it make a difference at all? Why do big sites seem to use these position classes?

I do lot of jQuery class-based searches if that is significant.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T11:12:47+00:00Added an answer on June 9, 2026 at 11:12 am

    In principle, it’s a bad idea. It’s not really any different from applying inline styles to all your elements. Best practice is good separation of style and content.

    As you’ve already mentioned, you will most likely need to change out loads of these classes later. It’s going to be a nightmare to maintain.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Something really weird is happening: when I call foo(100*1.0f), somewhere along the line that
Somewhere along the line I picked up the notion that using iframes is 'bad
Somewhere along the line from the DB to the application, this: sauté is getting
I've probably murdered the whole concept of MVC somewhere along the line, but my
I have an MVC application which uses a silverlight control. Somewhere along the line
Somewhere along the line, my app started crashing on the iPad though it still
Somewhere along the line, some huge, huge file got added to the git repository
(big) (big) Somewhere along the way into the function animationWithFrames , my vector loses
My custom error messages quit working somewhere along the way and I'm getting this
I am currently learning backbone.js via a screencast tutorial, somewhere along the way, my

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.