Bugzilla

The Font Editor writes property value changes to an element's inline style. This is done to ensure "the what you see is what you get" user expectations when editing a value, regardless of the origin of that property in the CSS cascade.

Pseudo-elements do not have an inline style that can be written to. The simple solution is to treat them in the Font Editor as unsupported element types, like comment nodes.

However, pseudo-elements may have font properties attached. Their use with icon fonts is a notable use case. Users want to be able to at least inspect the fonts and font properties applied to the selected pseudo-element.

We should provide this information for pseudo-elements in the Font Editor in a read-only mode (and include a note) until we implement a way to write value changes to individual CSS style rules instead of element inline styles.

The Font Editor writes property value changes to an element's inline style. This is done to ensure the "what you see is what you get" user expectation when editing a property value regardless of its origin within the CSS cascade.

Pseudo-elements do not have an inline style that can be written to. The simple solution is to treat them in the Font Editor as unsupported element types, like comment nodes.

However, pseudo-elements may have font properties attached. Their use with icon fonts is a notable use case. Users want to be able to at least inspect the fonts and font properties applied to the selected pseudo-element.

We should provide this information for pseudo-elements in the Font Editor in a read-only mode (and include a note) until we implement a way to write value changes to individual CSS style rules instead of element inline styles.