scraperwiki / scraperstrap Goto Github PK

Why's it there anyway? To clear enclosed floats? Bah. Get rid of it. I keep having to override it in my custom stylesheets.

Search inputs have a padding-left: 30px, which is 24px larger than normal.

Because of the stupid CSS box-model, padding is included in element width, meaning all search inputs are now 24px wider than expected.

This is fine in free-floating forms, but everywhere else the new, wider search inputs stick out like a sore thumb. eg: .form-horizontal, .span1 etc

bootstrap.css defines .container to be 940px. All of the .spanN measurements are based off this.

scraperstrap.css specifies four breakpoints, based on multiples of 300:

• 0–619px (320px container width)
• 620–919px (620px container width)
• 920–1219px (920px container width)
• 1220px+ (1220px container width)

While we're at it, bootstrap-responsive.css, if we wanted to include it, sets breakpoints at:

• 0–767px (100% container width)
• 768–979px (724px container width)
• 980–1199px (940px container width)
• 1200px+ (1170px container width)

We need to work out a way to make bootstrap containers and scraperstrap containers coexist harmoniously. Possibly by defining our own .spanN measurements (eeeek).