StyleSheet.js revision 32c7d588520dd01df70660506aa42076ca510c0c
var d = document,
sheets = {},
ssId = 0,
var p;
}
switch (prop) {
case 'opacity':
case 'font' :
break;
default :
for (p in style) {
style[p] = '';
}
}
}
}
} :
}
if (prop === 'opacity') {
} else {
}
}
};
var head,
node,
cssRules = {},
// Factory or constructor
if (!(this instanceof Y.StyleSheet)) {
}
if (!head) {
// TODO: do something. Preferably something smart
throw new Error('HEAD element not found to append STYLE node');
}
}
}
if (typeof seed === 'string') {
// Create entire sheet from seed cssText
// Not a load-time fork because low run-time impact and IE fails
// test for s.styleSheet at page load time (oddly)
if (node.styleSheet) {
} else {
}
return s;
} else if (!name) {
}
}
// styleSheet isn't available on the style node in FF2 until appended
// to the head element. style nodes appended to body do not affect
// change in Safari.
}
// IE stores StyleSheet under the "styleSheet" property
// IE stores the rules collection under the "rules" property
// IE supports removeRule
function (i) { sheet.deleteRule(i); } :
function (i) { sheet.removeRule(i); };
// IE supports addRule with different signature
// Initialize the cssRules map from the node
// TODO if xdomain link node, copy to a local style block and replace the
// link node with the style node. CAVEAT: alternate stylesheet, @media
var i,r,sel;
sel = r.selectorText;
_deleteRule(i);
} else {
}
}
// Cache the sheet by the generated Id
if (name) {
}
// Public API
Y.mix(this,{
// while disabled.
// Update cssText for a rule. Add the rule if it's not present already
// TODO: test for breakage in funny selectors ##i:go-..\\bo\om or valid
// (i think) #i\:go\-\.\.\\\\bo\\om
idx;
// Opera throws an error if there's a syntax error in the cssText.
// Should I do something about it, or let the error happen?
if (rule) {
} else {
// Safari replaces the rules collection, but maintains the rule
}
return this;
},
// remove rule properties or an entire rule
rules, i;
if (rule) {
if (!remove) {
}
}
} else {
remove = true;
}
}
if (remove) { // remove the rule altogether
_deleteRule(i);
break;
}
}
}
}
return this;
}
},true);
};
}
}
}
};
// input object's integrity, but if float and opacity are set, the input will
// be copied twice in IE. Is there a way to avoid this without increasing the
// byte count?
if ('opacity' in css) {
});
}
};
};
/*
NOTES
* Style node must be added to the head element. Safari does not honor styles
applied to StyleSheet objects on style nodes in the body.
* StyleSheet object is created on the style node when the style node is added
to the head element in Firefox 2 (and maybe 3?)
* The cssRules collection is replaced after insertRule/deleteRule calls in
Safari 3.1. Existing Rules are used in the new collection, so the collection
cannot be cached, but the rules can be.
* Opera requires that the index be passed with insertRule.
* Same-domain restrictions prevent modifying StyleSheet objects attached to
link elements with remote href (or "about:blank" or "javascript:false")
* IE names StyleSheet related properties and methods differently (see code)
* IE converts tag names to upper case in the Rule's selectorText
* IE converts empty string assignment to complex properties to value settings
for all child properties. E.g. style.background = '' sets non-'' values on
style.backgroundPosition, style.backgroundColor, etc. All else clear
style.background and all child properties.
* IE assignment style.filter = '' will result in style.cssText == 'FILTER:'
only opacity needing to be accounted for.
* Benchmarks of style.property = value vs style.cssText += 'property: value'
indicate cssText is slightly slower for single property assignment. For
multiple property assignment, cssText speed stays relatively the same where
style.property speed decreases linearly by the number of properties set.
Exception being Opera 9.27, where style.property is always faster than
style.cssText.
* Opera 9.5b throws a syntax error when assigning cssText with a syntax error.
* Opera 9.5 doesn't honor rule.style.cssText = ''. Previous style persists.
You have to remove the rule altogether.
* Stylesheet properties set with !important will trump inline style set on an
element or in el.style.property.
* Creating a worker style collection like document.createElement('p').style;
will fail after a time in FF (~5secs of inactivity). Property assignments
will not alter the property or cssText. It may be the generated node is
garbage collected and the style collection becomes inert (speculation).
* When creating an entire sheet at once, only FF2/3 & Opera allow creating a
style node, setting its innerHTML and appending to head.
* When creating an entire sheet at once, Safari requires the style node to be
created with content in innerHTML of another element.
* When creating an entire sheet at once, IE requires the style node content to
be set via node.styleSheet.cssText
* When creating an entire sheet at once in IE, styleSheet.cssText can't be
* When creating an entire sheet at once in IE, load-time fork on
var styleNode = d.createElement('style'); _method = styleNode.styleSheet ?..
fails (falsey). During run-time, the test for .styleSheet works fine
* Setting complex properties in cssText will SOMETIMES allow child properties
to be unset
set unset FF2 FF3 S3.1 IE6 IE7 Op9.27 Op9.5
---------- ----------------- --- --- ---- --- --- ------ -----
border -top NO NO YES YES YES YES YES
-top-color NO NO YES YES YES
-color NO NO NO NO NO
background -color NO NO YES YES YES
-position NO NO YES YES YES
-position-x NO NO NO NO NO
font line-height YES YES NO NO NO NO YES
-style YES YES NO YES YES
-size YES YES NO YES YES
-size-adjust ??? ??? n/a n/a n/a ??? ???
padding -top NO NO YES YES YES
margin -top NO NO YES YES YES
list-style -type YES YES YES YES YES
-position YES YES YES YES YES
overflow -x NO NO YES n/a YES
??? - unsetting font-size-adjust has the same effect as unsetting font-size
*/