Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/4ae9b8/browserhacks
An extensive list of CSS/JS browserhacks from all over the interwebs.
https://github.com/4ae9b8/browserhacks
Last synced: about 2 months ago
JSON representation
An extensive list of CSS/JS browserhacks from all over the interwebs.
- Host: GitHub
- URL: https://github.com/4ae9b8/browserhacks
- Owner: 4ae9b8
- Created: 2012-12-29T14:55:59.000Z (almost 12 years ago)
- Default Branch: gh-pages
- Last Pushed: 2023-01-07T10:10:16.000Z (almost 2 years ago)
- Last Synced: 2024-08-01T08:06:39.622Z (4 months ago)
- Language: JavaScript
- Homepage: http://browserhacks.com/
- Size: 7.72 MB
- Stars: 1,265
- Watchers: 79
- Forks: 149
- Open Issues: 48
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-github-repos - 4ae9b8/browserhacks - An extensive list of CSS/JS browserhacks from all over the interwebs. (JavaScript)
- awesome-starred - 4ae9b8/browserhacks - An extensive list of CSS/JS browserhacks from all over the interwebs. (others)
README
Browserhacks.com
================
What’s this?
------------
Browserhacks is an extensive list of browser specific CSS and JavaScript hacks from all over the interwebs.
Please keep in mind using a hack is not always the perfect solution. It can be useful to fix some weird browser specific bug, but in most cases you should fix your CSS/JS.
How to?
-------
1. Pick the hack you want
2. Copy it into your stylesheet
3. Add the styles you want between the braces
4. Enjoy the new styles for the browser you targeted!
Created by
---------
* [Tim Pietrusky](http://twitter.com/timpietrusky)
* [Kitty Giraudel](http://twitter.com/KittyGiraudel)
* [Fabrice Weinberg](http://twitter.com/fweinb)
Updates by
---------
* [Jeff Clayton](https://github.com/jeffclayton)
Thanks to
---------
* [Joshua Hibbert](https://twitter.com/_joshnh) for the design
* [Jeff Clayton](https://github.com/jeffclayton) for his help with testing hacks and creating new ones, now also an administrator
* [Sara Soueidan](http://twitter.com/sarasoueidan), [Ana Tudor](http://twitter.com/thebabydino), [Mads Cordes](http://twitter.com/mobilpadde) for their kind help
* [Paul Irish](http://twitter.com/paul_irish) for [his great post on CSS hacks](http://www.paulirish.com/2009/browser-specific-css-hacks/)
* [Keith Clarke](http://twitter.com/keithclarkecouk) for [his @media block CSS hacks](http://blog.keithclark.co.uk/moving-ie-specific-css-into-media-blocks/)
* [Nicolas Gallagher](http://twitter.com/necolas) for [his IE CSS hacks](https://gist.github.com/necolas/983116)
* And various nice contributors :)
Deployment
----------
The site is a Jekyll setup hosted on GitHub Pages. Simply update the `gh-pages` branch to update the site (direct edit on GitHub, manual push or pull-request merge).
Adding new hacks
----------------
Adding a new hack is as simple as adding a new entry in [`_data/hacks.json`](https://github.com/4ae9b8/browserhacks/blob/gh-pages/_data/hacks.json). Like this:
```json
{
"type": "selector",
"browsers": {
"ch": "*",
"op": "14+"
},
"label": "A label for your hack if necessary.",
"language": "css",
"code": [
".selector:not(*:root) {}"
],
"test": [
".selector:not(*:root) { background: lightgreen; }"
]
}
```
The **type** key defines which type of hack it is; valid types are listed in [`_data/hackTypes.json`](https://github.com/4ae9b8/browserhacks/blob/gh-pages/_data/hackTypes.json).
The **browsers** key is an object mapping a browser’s shortname to a version expression; valid browsers are listed in [`_data/browsers.json`](https://github.com/4ae9b8/browserhacks/blob/gh-pages/_data/browsers.json). Versions can be:
* strict version (e.g. `42`)
* strict versiond (e.g. `42|43`)
* version and up (e.g. `42+`)
* version and below (e.g. `42-`)
* any version (e.g. `*`)
The **label** key can be left empty, or describe the hack if it is necessary.
The **language** key defines how to display the hack, and how to create the dynamic test for it. Possible languages are `css`, `javascript` and `markup`.
The **code** key is an array of expressions for the hack. Certain hacks can be written in several forms, hence the need for an array.
The **test** key is an array of expressions for the test. It should be a direct copy of the `code` array, except the braces should be filled with a `background: lightgreen;` in case of a selector, or `.selector { background: lightgreen; }` in case of a media expression. Take example on other existing hacks.
Once you’ve done that, simply run `npm run build` to complete the hack with a unique ID, a human-readable version, a check for whether or not it’s a legacy hack, and create dynamic tests.