Isaac Muse

The experimental branch is up via PR #228. No tests are currently present, but it does appear to work as described in the CSS document. I've seen the selector described...

This still hasn't formally made it into the spec. It may never. We wanted to get the jump on this, but there seems to be very little interest from the...

I guess you could get away with something like `:contains(text i, "more text" i)`. It is easy enough to parse, just not sure how I feel about it though.

While this may still be worth doing, if we decide to move forward with #175, you could work around this with case insensitive regex. Going either way with these is...

It's important to note Beautiful Soup already provides regex, we don't **need** this, but it might be nice to incorporate regex in some way for selectors as well. We just...

If we do this, a name like `:contains-regexp()` might be more descriptive and make more sense. When defining regex keywords, should we require them to be in the form of...

Thinking about this more, we really could use custom selectors to do regex. Currently we take a string for a given custom pseudo-class, but we could accept an custom pseudo-class...

Another possibility is to extend contains and the attribute equal case to accept custom template variables: `$var`. You would define regular expressions with custom variable names which could be a...

If we end up doing #175, this would not be needed.

It seems an example has been added over at the CSS drafts page: https://drafts.csswg.org/selectors-4/#placeholder. It mentions: ``` For example, according to the semantics of [HTML] the placeholder attribute on the...