2012-07-19 00:11:26 +00:00
|
|
|
/**
|
|
|
|
|
* VisualEditor initialization ViewPageTarget styles.
|
2012-07-19 21:25:16 +00:00
|
|
|
*
|
2012-07-19 00:11:26 +00:00
|
|
|
* @copyright 2011-2012 VisualEditor Team and others; see AUTHORS.txt
|
|
|
|
|
* @license The MIT License (MIT); see LICENSE.txt
|
|
|
|
|
*/
|
|
|
|
|
|
2012-06-18 20:12:32 +00:00
|
|
|
.ve-surface {
|
|
|
|
|
margin-top: 0.8em;
|
|
|
|
|
}
|
|
|
|
|
|
2012-06-11 06:54:41 +00:00
|
|
|
.es-toolbar-wrapper {
|
2012-06-14 01:26:21 +00:00
|
|
|
margin: -1em -1em 1em -1em;
|
2012-07-26 18:47:11 +00:00
|
|
|
position: relative;
|
2012-05-31 00:09:06 +00:00
|
|
|
}
|
2012-06-11 06:54:41 +00:00
|
|
|
|
|
|
|
|
.es-toolbar {
|
2012-06-14 01:26:21 +00:00
|
|
|
display: none;
|
2012-06-11 06:54:41 +00:00
|
|
|
margin-left: 1px;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-pageTitle {
|
2012-06-14 21:31:08 +00:00
|
|
|
-webkit-transition: opacity 200ms ease-out;
|
|
|
|
|
-moz-transition: opacity 200ms ease-out;
|
|
|
|
|
-o-transition: opacity 200ms ease-out;
|
|
|
|
|
transition: opacity 200ms ease-out;
|
2012-06-14 01:26:21 +00:00
|
|
|
cursor: default;
|
2012-06-12 01:21:31 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-pageToc {
|
2012-06-14 21:31:08 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
overflow: hidden;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-loadingSpinner {
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
/* @embed */
|
2012-06-11 20:24:20 +00:00
|
|
|
background-image: url(images/loading.gif);
|
|
|
|
|
width: 128px;
|
|
|
|
|
height: 15px;
|
|
|
|
|
float: right;
|
2012-06-11 06:54:41 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-feedbackButton {
|
2012-06-28 09:53:54 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
cursor: pointer;
|
|
|
|
|
vertical-align: top;
|
|
|
|
|
padding: 0.25em;
|
|
|
|
|
height: 22px;
|
|
|
|
|
margin-right: 0.25em;
|
|
|
|
|
border: solid 1px transparent;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-feedbackButton a {
|
2012-06-28 09:53:54 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
vertical-align: middle;
|
|
|
|
|
height: 32px;
|
|
|
|
|
padding-left: 4px;
|
|
|
|
|
padding-right: 4px;
|
|
|
|
|
font-size: 0.8em;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton {
|
2012-05-31 00:09:06 +00:00
|
|
|
display: inline-block;
|
2012-07-10 14:08:58 +00:00
|
|
|
border: solid 1px #c3e59a;
|
|
|
|
|
-webkit-border-radius: 0.25em;
|
|
|
|
|
-moz-border-radius: 0.25em;
|
|
|
|
|
-o-border-radius: 0.25em;
|
|
|
|
|
border-radius: 0.25em;
|
2012-05-31 00:09:06 +00:00
|
|
|
cursor: pointer;
|
|
|
|
|
vertical-align: top;
|
2012-07-10 14:08:58 +00:00
|
|
|
font-size: 1em;
|
|
|
|
|
padding: 0.25em 0.5em;
|
2012-05-31 00:09:06 +00:00
|
|
|
height: 22px;
|
2012-06-01 23:26:03 +00:00
|
|
|
margin-right: 0.25em;
|
2012-07-10 14:08:58 +00:00
|
|
|
/* Fancy CSS background */
|
|
|
|
|
background-image: -webkit-gradient(
|
|
|
|
|
linear,
|
|
|
|
|
left bottom,
|
|
|
|
|
left top,
|
|
|
|
|
color-stop(0, #c3e59a),
|
|
|
|
|
color-stop(1, #f0fbe1)
|
|
|
|
|
);
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
background-image: -webkit-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -moz-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -ms-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -o-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
2012-05-31 00:09:06 +00:00
|
|
|
}
|
2012-06-12 01:21:31 +00:00
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton:before {
|
2012-05-31 00:09:06 +00:00
|
|
|
content: " ";
|
|
|
|
|
position: absolute;
|
|
|
|
|
display: block;
|
|
|
|
|
height: 22px;
|
|
|
|
|
}
|
2012-06-12 01:21:31 +00:00
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton:hover {
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
border-color: #eee;
|
2012-05-31 00:09:06 +00:00
|
|
|
}
|
2012-06-12 01:21:31 +00:00
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton:active,
|
|
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton-down {
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
border-color: #ddd;
|
2012-05-31 00:09:06 +00:00
|
|
|
-webkit-box-shadow: inset 0px 1px 4px 0px rgba(0, 0, 0, 0.07);
|
|
|
|
|
-moz-box-shadow: inset 0px 1px 4px 0px rgba(0, 0, 0, 0.07);
|
|
|
|
|
box-shadow: inset 0px 1px 4px 0px rgba(0, 0, 0, 0.07);
|
2012-05-31 23:54:53 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton-disabled {
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
filter: alpha(opacity=50);
|
2012-06-12 17:32:10 +00:00
|
|
|
opacity: 0.5;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton-label {
|
2012-06-12 01:21:31 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
vertical-align: middle;
|
|
|
|
|
height: 32px;
|
|
|
|
|
padding-left: 4px;
|
2012-06-11 06:54:41 +00:00
|
|
|
font-size: 0.8em;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* mini save button */
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-closeButton {
|
2012-06-11 06:54:41 +00:00
|
|
|
right: .025em;
|
|
|
|
|
width: 22px;
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
/* @embed */
|
2012-07-20 23:59:59 +00:00
|
|
|
background-image: url(../../../ui/styles/images/close.png);
|
2012-06-11 06:54:41 +00:00
|
|
|
background-position: center center;
|
2012-05-31 23:54:53 +00:00
|
|
|
background-repeat: no-repeat;
|
|
|
|
|
}
|
2012-06-11 06:54:41 +00:00
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton {
|
2012-05-31 23:54:53 +00:00
|
|
|
position: absolute;
|
2012-06-18 20:12:32 +00:00
|
|
|
cursor: pointer;
|
|
|
|
|
border: 1px solid #c3e59a;
|
2012-05-31 23:54:53 +00:00
|
|
|
margin-top: 10px;
|
|
|
|
|
right: 10px;
|
2012-06-11 06:54:41 +00:00
|
|
|
font-size: 1em;
|
|
|
|
|
padding: 0.5em 1em;
|
2012-07-10 14:08:58 +00:00
|
|
|
-webkit-border-radius: 0.25em;
|
2012-06-11 06:54:41 +00:00
|
|
|
-moz-border-radius: 0.25em;
|
2012-07-10 14:08:58 +00:00
|
|
|
-o-border-radius: 0.25em;
|
|
|
|
|
border-radius: 0.25em;
|
2012-05-31 23:54:53 +00:00
|
|
|
/* Fancy CSS background */
|
|
|
|
|
background-image: -webkit-gradient(
|
|
|
|
|
linear,
|
|
|
|
|
left bottom,
|
|
|
|
|
left top,
|
2012-06-18 20:12:32 +00:00
|
|
|
color-stop(0, #c3e59a),
|
|
|
|
|
color-stop(1, #f0fbe1)
|
2012-05-31 23:54:53 +00:00
|
|
|
);
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
background-image: -webkit-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -moz-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -ms-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: -o-linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
|
|
|
|
background-image: linear-gradient(bottom, #c3e59a 0%, #f0fbe1 100%);
|
2012-05-31 23:54:53 +00:00
|
|
|
}
|
2012-06-12 01:21:31 +00:00
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton:active,
|
|
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-down {
|
2012-06-19 19:15:41 +00:00
|
|
|
/* Fancy CSS background */
|
|
|
|
|
background-image: -webkit-gradient(
|
|
|
|
|
linear,
|
|
|
|
|
left bottom,
|
|
|
|
|
left top,
|
|
|
|
|
color-stop(0, #f0fbe1),
|
|
|
|
|
color-stop(1, #c3e59a)
|
|
|
|
|
);
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
background-image: -webkit-linear-gradient(bottom, #f0fbe1 0%, #c3e59a 100%);
|
|
|
|
|
background-image: -moz-linear-gradient(bottom, #f0fbe1 0%, #c3e59a 100%);
|
|
|
|
|
background-image: -ms-linear-gradient(bottom, #f0fbe1 0%, #c3e59a 100%);
|
|
|
|
|
background-image: -o-linear-gradient(bottom, #f0fbe1 0%, #c3e59a 100%);
|
|
|
|
|
background-image: linear-gradient(bottom, #f0fbe1 0%, #c3e59a 100%);
|
2012-06-19 19:15:41 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton:hover {
|
2012-06-18 20:12:32 +00:00
|
|
|
border-color: #a7cd76;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-saving,
|
|
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-saving:hover {
|
2012-06-19 19:15:41 +00:00
|
|
|
background-color: #e6f2cc;
|
|
|
|
|
background-image: none;
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
color: #ccc;
|
2012-06-19 19:15:41 +00:00
|
|
|
border-color: #e3f0c6;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-toolbar-saveButton-icon,
|
|
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-icon {
|
2012-06-11 06:54:41 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
vertical-align: middle;
|
|
|
|
|
height: 2em;
|
|
|
|
|
width: 28px;
|
2012-06-18 20:12:32 +00:00
|
|
|
margin-right: -4px;
|
2012-05-31 23:54:53 +00:00
|
|
|
background: transparent;
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
/* @embed */
|
2012-07-20 23:59:59 +00:00
|
|
|
background-image: url(../../../ui/styles/images/accept-clear.png);
|
2012-06-12 01:21:31 +00:00
|
|
|
background-position: right top;
|
2012-05-31 23:54:53 +00:00
|
|
|
background-repeat: no-repeat;
|
2012-06-11 06:54:41 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-label {
|
2012-07-10 14:08:58 +00:00
|
|
|
display: inline-block;
|
|
|
|
|
vertical-align: middle;
|
|
|
|
|
height: 32px;
|
|
|
|
|
line-height: 2.125em;
|
|
|
|
|
padding-left: 4px;
|
|
|
|
|
font-size: 1.2em;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-saving
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-saveButton-icon {
|
|
|
|
|
/* @embed */
|
2012-06-19 19:15:41 +00:00
|
|
|
background-image: url(images/saving.gif);
|
|
|
|
|
background-position: right 46%;
|
|
|
|
|
}
|
|
|
|
|
|
2012-06-11 06:54:41 +00:00
|
|
|
/* Save dialog styles */
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog {
|
2012-06-13 21:44:39 +00:00
|
|
|
display: none;
|
2012-06-12 17:32:10 +00:00
|
|
|
top: 0.25em;
|
2012-06-12 01:21:31 +00:00
|
|
|
right: 0.5em;
|
2012-06-11 06:54:41 +00:00
|
|
|
width: 29em;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-body {
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
border-top: 1px solid #ddd;
|
2012-06-11 06:54:41 +00:00
|
|
|
padding: 10px 0;
|
|
|
|
|
font-size: 12px;
|
|
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-license {
|
2012-06-11 06:54:41 +00:00
|
|
|
font-size: 0.7em;
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
color: #999;
|
2012-06-11 06:54:41 +00:00
|
|
|
}
|
|
|
|
|
|
2012-07-20 23:59:59 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog-options {
|
2012-06-11 06:54:41 +00:00
|
|
|
float: left;
|
|
|
|
|
}
|
|
|
|
|
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog input[type="text"] {
|
2012-06-18 20:12:32 +00:00
|
|
|
width: 98%;
|
2012-06-11 06:54:41 +00:00
|
|
|
font-size: 12px;
|
|
|
|
|
padding: 4px;
|
|
|
|
|
margin: 10px 0;
|
|
|
|
|
}
|
|
|
|
|
|
Kranitor #3: jQuerlyfornication ft. The Cascaders
* Classicifation (JS)
Use addClass instead of attr( 'class' ) whenever possible.
addClass will manipulate the properties directly instead of
(re-)setting an attribute which (most) browsers then sync
with the properties.
Difference between:
elem.className
and
elem.setAttribute( 'class', .. );
Just like .checked, .value, .disabled and other interactive
properties, the HTML attributes should only be used for initial
values from the html document. When in javascript, only set
properties. Attributes are either ignored or slow.
* Styling (JS)
Use .css() instead of attr( 'style' ).
Again, setting properties instead of attributes is much faster,
easier and safer. And this way it takes care of cross-browser
issues where applicable, and less prone to error due to dealing
with key-value pairs instead of css strings.
Difference between:
elem.style.foo = 'bar';
and
elem.setAttribute( 'style', 'foo: bar;' );
* Finding (JS)
Use .find( 'foo bar' ) instead of .find( 'foo' ).find( 'bar' ).
It is CSS!
* Vendor prefixes (CSS)
It is important to always list newer (standards-compliant) versions
*after* the older/prefixed variants.
See also http://css-tricks.com/ordering-css3-properties/
So the following three:
-webkit-gradient (Chrome, Safari 4)
-webkit-linear-gradient (Chrome 10, Safari 5+)
linear-gradient (CSS3 standard)
... must be in that order.
Notes:
- "-moz-opacity" is from before Mozilla 1.7 (Firefox < 0.8)
Has not been renamed to "opacity" since Firefox 0.9.
- Removed redundant "-moz-opacity"
- Added "filter: alpha(opacity=**);" where missing
- Fixed order of css3 properties (old to new)
- Add standardized css3 versions where missing
(some 'border-radius' groups didn't have the non-prefixed version)
- Spacing
- @embed
- Shorten hex colors where possible (#dddddd -> #ddd)
$ ack '#([0-9a-f])\1{5}' --css
$ ack '#([0-9a-f])\1{2};' --css
Change-Id: I386fedb9058c2567fd0af5f55291e9859a53329d
2012-07-28 19:15:23 +00:00
|
|
|
.ve-init-mw-viewPageTarget-saveDialog input[type="checkbox"] {
|
2012-06-11 06:54:41 +00:00
|
|
|
margin-right: 5px;
|
|
|
|
|
}
|