Bug 1590884 Comment 22 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Magnus, we now allow label:not([value]) and description:not([value]) to get their CSS display value overridden by other stylesheets. So if some CSS on your side did that before, it will now actually have an effect (unlike before where only display: none worked).

This caused bug 1694936 on our side.

The default behaviour of label:not([value]) and description:not([value]) remains unchanged however.
Revision 1 by
on 
Magnus, we now allow label:not([value]) and description:not([value]) to get their CSS display value overridden by other stylesheets. So if some CSS on your side did that before, it will now actually have an effect (unlike before where only display: none worked).

This caused bug 1694936 on our side. You may want to check if there was some previously useless override that suddenly turned active.

The default behaviour of label:not([value]) and description:not([value]) remains unchanged however.
Revision 2 by
on 
Magnus, we now allow label:not([value]) and description:not([value]) to get their CSS display value overridden by other stylesheets. So if some CSS on your side did that before, it will now actually have an effect (unlike before where only display: none worked).

This caused bug 1694936 on our side. You may want to check if there was some display override that suddenly turned active.

The default behaviour of label:not([value]) and description:not([value]) remains unchanged however.

Back to Bug 1590884 Comment 22