Determine whether a selector contains a pseudo-class
A query library for ECMAScript AST using a CSS selector like query language.
Style elements relative to other elements in CSS
a CSS selector parser
A pseudo-class for matching elements in a selector list
Use the :any-link pseudo-class in CSS
Style form elements when they are empty
Use the :dir pseudo-class in CSS
Extended W3C Selectors matcher
The Reference Element Pseudo-class: :scope
Selectors decision tree - choose matching selectors, fast
Storybook Pseudo-states addon: Manipulate CSS pseudo states
A CSS selector engine.
Determine whether a selector contains a pseudo-element.
pseudo-localization for internationalization testing
Pseudolocalization plugin for i18next
PostCSS plugin to transform the :is() CSS pseudo-class into more compatible CSS selectors.
A library for arbitrary-precision decimal and non-decimal arithmetic
Streaming http in the browser
Use the :focus-visible pseudo-selector in CSS
Use the :focus-within pseudo-selector in CSS
Strict TypeScript and Flow types for style based on MDN data
Bringing Classes to Inline Styles
A stylelint plugin that enforces the use of ampersands in front of pseudo selectors
This gem is intended to be used in Rails pre-processing, after the page has been generated but before it is delivered to the requestor. It does a case-insensitive search in the source text for the pseudo-tag <toc />, which marks where the table of contents will be placed. If the tag is not found, the unmodified source is returned. If the tag is found, it searches the text for header tags in a given range, and add an id attribute if the header does not already have one. If no headers were found, it will remove the tag and return the modified source. If there are headers, a link is generated for each one, using the header's text and id for the link's text and href. The links are wrapped in some divs, with classes and ids added so the table of contents can be styled. The <toc /> pseudo-tag is then replaced with the table of contents, and the the modified source is returned.
GuerrillaRotate ============== This plugin lets you have multiple view pages for the one action, so that you can rotate through different views in order to test which one is the most effective. This is known as A/B testing, split testing or side-by-side testing. It will automatically switch between the different views for different web requests (uses .rand so is pseudo random, not round-robin or anything). The particular view is sticky for a (rails) session, so that once that view has been chosen for that visitor they will see the same, consistent view each time. It integrates automagically into [Rubaidh::GoogleAnalytics](http://github.com/rubaidh/google_analytics) by setting the override_trackpageview to the name of the unique view file (instead of the action-based URL) so you can track it easily in Google Analytics. Without that you'll want to track it by putting different tracking codes in each of your view templates. Example ------- So, in your views you will create some new templates with something (can be anything including nothing) between the template name and the first part of the extension. So you might have the following files for the products/index action: app/views/products/index.html.erb app/views/products/index_alt.html.erb app/views/products/index_new.html.erb Then all you need to do is tell your controller to rotate for that action: ### app/controllers/products_controller.rb class ProductsController < ApplicationController guerrilla_rotate :index, :show # etc.. end NB: guerrilla_rotate is also aliased as guerilla_rotate for the alternative spelling and typos. Copyright © 2009 Jason King, released under the MIT license