The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Have a look at the css grid (see, e.g. [here^]) layout system, if you havn't. Some proponents of it think it is css done right, to which I tend to agree.
While traditional css layout references the conents themselve, which could intefer or mess with each other and is harder to control, the css grid method separates coordination from the content. It enables a user to create lot simpler, more accurate and flexible layout systems ...
You can mix whatever grid system with css grid. css grid can be used either as a page level grid system or local grid system to construct controls, like the input group one, with ease (a three columns one row grid, but I haven't tried it). Hopefully it may solve your 1px off problem (I also experienced this problem before and haven't find it urgent enough to fix)
He faarrrkkkking well did and you got it right. Bloody Dutch bastards.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
Crikey! I bought my first in about 1999, and it took months to get it configured, using extensive help from the ISP and the SonicWall support experts (not first level). This one's no simpler, and it didn't come with a manual. Why do they have to make these machines so difficult set up? All acronyms, no explanations, and online help that is utterly useless - true Microsoft copies. It's an amazingly powerful machine for protecting a network, but how does one tell if it's been set up right, when everything is written in a foreign language? Grrrr....
The people who write technical manuals are often the people who write the software, and most of 'em have difficulty stringing two sentences together, much less thinking like a user! It's easy to understand - for them - because it is an abstract of the software, rather than something genuinely written to help a novice. And that's probably because it's documentation, and that's "boring" so it gets chucked together with as little effort as possible.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
I know how bad I'm when explaining technical things to non-technical people, so I constantly refuse to write documentation... The only kid of documentation I write is for fellow developers on the team...
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
I blame my instructor in college Technical Writing class. He warned me to never let anyone know what I can do (write well), else I'd never be allowed to design anything. Employers would stick me in a corner and make me write clear, accurate, and understandable tech manuals for the rest of my life. I guess he told too many students the same thing, and here we are today because of it.