CSS marquee-speed
The CSS marquee-speed property is used for specifying the speed of a marquee.
The marquee-speed property works in conjunction with the overflow, overflow-style, marquee-play-count, marquee-direction, and marquee-style properties.
What is a Marquee?
A marquee is an effect where the content within an HTML element moves - or "scrolls" - (either horizontally or vertically) so that eventually, all content has been displayed at least once. The content can keep scrolling or it can stop after a certain number of times. It can slide in and stop. It can bounce back and forth - either once or a pre-determined number of times.
How Do Marquees Work in CSS?
In CSS3, marquees work like this:
If the contents of an element are too large to fit inside the element, it is said to "overflow". The overflow property can be used to hide the parts that don't fit inside the box. Now the overflow-style property can be used to specify that a marquee should be used to display the content (a marquee-line for horizontally scrolling marquees and marquee-block for vertically scrolling marquees). The marquee-speed property specifies how fast the marquee should run. For example, the marquee could run slow, medium or fast.
Note that at the time of writing, browser support for CSS3 marquees is limited. Therefore, the examples on this page may not work as expected (at least until browsers start to support this property).
Also, this property is still under development by the W3C, which means that it may change at any time.
| Syntax: |
marquee-speed: value
|
|---|---|
| Example |
marquee-speed: fast;
|
| Try it yourself! |
|
| Possible Values: |
The value can be one of the following.
|
| Initial Value: | normal
|
| Applies to: | Non-replaced block-level elements and non-replaced 'inline-block' elements |
| Inherited: | No |
| Media: | Visual |
Browser Compatibility
At the time of writing, CSS3 was still under development and browser support for many CSS3 properties was limited or non-existent. For maximum browser compatibility many web developers add browser-specific properties by using extensions such as -webkit- for Safari and Google Chrome, -ms- for Internet Explorer, -moz- for Firefox, -o- for Opera etc. As with any CSS property, if a browser doesn't support a proprietary extension, it will simply ignore it.
This practice is not recommended by the W3C, however in many cases, the only way you can test a property is to include the CSS extension that is compatible with your browser.
Be aware that if you choose to use the proprietary CSS extensions in a live environment, your code will not pass any W3C CSS validation, as the browser-specific properties are not valid W3C properties.
Many of the CSS3 examples on this website include these browser specific properties. If they weren't included, most of the examples wouldn't work for most users (at least, not until possibly years after the article was written).
The major browser manufacturers are working to support the W3C properties, and eventually, you will be able to omit these browser-specific properties.