Interesting -moz CSS Properties

By  on  

I'm always on the lookout for interesting vendor-specific features and prefixes. The beauty in them is that they allow developers to enhance where possible; they aren't taken into account as core design, but provide nice little touches. I was poking around Mozilla's MDN and found a great list of proprietary -moz properties. Here are a few of that I found interesting and useful.

::-moz-list-bullet

::-moz-list-bullet allows developers to style the bullet bullet text in lists; not the content, but the bullet text itself:

ul.customList li::-moz-list-bullet {
	color: #999;
	font-size: 24px;
	text-decoration: underline;
}

-moz-force-broken-image-icon

Firefox presently displays alt text for every broken image on the page. This may not be helpful for the purposes of debugging because the text may blend into the page. By using -moz-force-broken-image-icon, you can fore the broken image icon instead of the alt text:

img {
	-moz-force-broken-image-icon: 1;
}

-moz-margin-start and -moz-margin-end

Both work very much like margin-left and margin-right, but reverse position when in RTL mode. Very useful if you're trying to create a flexible website built for LTR or RTL reading.

.myBlock {
	-moz-margin-start: 10px;
	-moz-margin-end: 5px;
}

-moz-orient

The -moz-orient property currently only applies to progressbar elements, allowing them to be vertical or horizontal:

progress.up {
	-moz-orient: vertical;
}

-moz-window-shadow

-moz-window-shadow specifies whether a window in OS X will have a shadow.

.panel {
	-moz-window-shadow: none;
}

There are a few hundred proprietary properties available so take a few moments and let me know if you find any of them interesting, and if you've used any of them for your projects!

Recent Features

  • By
    Introducing MooTools Templated

    One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating: new Element Madness The first way to create UI-driven...

  • By
    Create Namespaced Classes with MooTools

    MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does.  Many developers create their classes as globals which is generally frowned up.  I mostly disagree with that stance, but each to their own.  In any event...

Incredible Demos

  • By
    Introducing MooTools ScrollSidebar

    How many times are you putting together a HTML navigation block or utility block of elements that you wish could be seen everywhere on a page? I've created a solution that will seamlessly allow you to do so: ScrollSidebar. ScrollSidebar allows you...

  • By
    Drag. Drop. Lock.

    I've received dozens of emails about my Six Degrees of Kevin Bacon Using MooTools article. The MooTools in my article contained a lot of conditional code to require correct dropping per the game and many people requested that I simplify the process and just...

Discussion

  1. Fabian

    You should change the ol to ul in ol.customList li::-moz-list-bullet, as it’s just working on bullets (imho).

    • Updated. Thanks for having a humble opinion. ;)

  2. Would be nice if you provided some demos, e.g. links to quick jsFiddle tests :)

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!