Difference between revisions of "CSS Checker JetPack Extension"
Knovichikhi (talk | contribs) (→Project News) |
Knovichikhi (talk | contribs) (→Project News) |
||
Line 48: | Line 48: | ||
* [http://manoutoftime.wordpress.com/2010/10/22/release-0-1 0.1 Release] | * [http://manoutoftime.wordpress.com/2010/10/22/release-0-1 0.1 Release] | ||
* [http://github.com/manoutoftime/cssChecker GitHub Repo] | * [http://github.com/manoutoftime/cssChecker GitHub Repo] | ||
+ | * [http://manoutoftime.wordpress.com/2010/11/15/release-0-2/ 0.2 Release] | ||
+ | * [http://manoutoftime.wordpress.com/2010/12/05/release-0-3/ 0.3 Release - UI, Rewriting of 0.1 and 0.2] | ||
+ | * [http://manoutoftime.wordpress.com/2010/12/10/release-0-3-1/ 0.3.1 Release - Rewriting of 0.1 and 0.2, Updates for Add-on SDK 1.0] |
Revision as of 11:11, 16 December 2010
Contents
Project Name
CSS Checker JetPack Extension 0.1
Project Description
CSS as a standard evolves more slowly than browser vendor implementations, and as such, browser extensions are created. For example: -moz-box-shadow (Mozilla only), -webkit-box-shadow (Chrome/Safari), box-shadow (CSS standard). This extension will allow the user to tell when a a -webkit-* extension is being used for which there is also a -moz-* version. This will help with finding compatibility issues on websites that appear to work in one browser and not another.
Resources
- Vendor Specific Extensions:
- JetPack SDK
- https://jetpack.mozillalabs.com/
- IRC in #jetpack on irc.mozilla.org
- Gecko Layout Engine
- Mozilla CSS Extensions
- WebKit Layout Engine
- Webkit CSS Extensions
Project Leader(s)
Project Contributor(s)
Project Details
Release 0.1 The extension is based on JetPack SDK and packaged as standard FF extension in a xpi archive.
The way it works: On tab load, it will parse page style sheets all the way down to X CSS properties. It will then get that CSS property selector and convert it to xpath. Firefox xpath evaluator interface will then build a list of matching DOM elements. The problem right now is to get webkit properties from style sheet, since those are ignored by Firefox nsCSSScanner.