This is a fairly common question, and there isn't a One True Answer.
These are the most common techniques:
ּ_בּ | |
בּ_בּ | |
טּ_טּ | |
כּ‗כּ | |
לּ_לּ | |
מּ_מּ | |
סּ_סּ | |
תּ_תּ | |
٩(×̯×)۶ | |
٩(̾●̮̮̃̾•̃̾)۶ |
<!DOCTYPE html> | |
<html> | |
<head> | |
<style> | |
/* How to select a range of children | |
* (Here, 3rd-7th children, inclusive): | |
*/ | |
ul li:nth-child(n+3):nth-child(-n+7) { | |
outline: 1px solid #0f0; | |
} |
# This is a total hack to slow down webdriver in Capybara | |
# so you can more easily watch what is happening. | |
# paste this above the top of a Capybara Webdriver RSpec test if you need to debug something in slo-mo | |
require 'selenium-webdriver' | |
module ::Selenium::WebDriver::Remote | |
class Bridge | |
def execute(*args) |
stylus: | |
compress: true | |
path: ./path/to/styl |
// #### it's compilable -prefix-free | |
// © 2011 Artem Sapegin http://sapegin.ru | |
// + 2011 Grawl http://grawl.ru | |
// + radial-gradient and other rules with vendor prefixes added by Grawl. | |
// add your fixes to My table of vendor prefixes there: http://goo.gl/3hPfR | |
/* mask: | |
parameter() | |
-webkit-parameter arguments | |
-moz-parameter arguments | |
-ms-parameter arguments |
OOCSS is awesome because it helps us organize our style sheets in clean and simple ways but it can be far too rigid for the new responsive web. How can we use preprocessors to preserve both flexibility and cleanliness of code? Can these objects be abstracted to our preprocessors?
Lets first take a look at three column widths in OOCSS to see how they compare.
CSS
I spent a lot of time trying to find a pretty optimal (for me) setup for Clojure… at the same time I was trying to dive in and learn it. This is never optimal; you shouldn't be fighting the environment while trying to learn something.
I feel like I went through a lot of pain searching Google, StackOverflow, blogs, and other sites for random tidbits of information and instructions.
This is a comprehensive "what I learned and what I ended up doing" that will hopefully be of use to others and act as a journal for myself if I ever have to do it again. I want to be very step-by-step and explain what's happening (and why) at each step.
An ongoing project to catalogue all of these sneaky, hidden, bleeding edge selectors as I prepare my JSConf EU 2012 talk.
Everything is broken up by tag, but within each the selectors aren't particularly ordered.
I have not tested/verified all of these. Have I missed some or got it wrong? Let me know. - A
A friendly reminder that you may need to set this property on your target/selected element to get the styling results you want:
-webkit-appearance:none;
var CP = window.CanvasRenderingContext2D && CanvasRenderingContext2D.prototype; | |
if (CP && CP.lineTo){ | |
CP.dashedLine = function(x,y,x2,y2,dashArray){ | |
if (!dashArray) dashArray=[10,5]; | |
if (dashLength==0) dashLength = 0.001; // Hack for Safari | |
var dashCount = dashArray.length; | |
this.moveTo(x, y); | |
var dx = (x2-x), dy = (y2-y); | |
var slope = dy/dx; | |
var distRemaining = Math.sqrt( dx*dx + dy*dy ); |