Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Default Property Values Not Showing On Firefox Dev Edition

  • No replies
  • 1 has this problem
  • 2 views
more options

Firefox Dev Ed is a great browser for web development and tweaking CSS. But sadly it does not always show default property values.

A classic example of this is the
    element's default padding-left property. This apparently is set at 40px automatically unless overridden by the web designer. I think that ALL inherited or default properties of elements ought to be clearly shown in the inspect tool's styling listings. You could spend hours maddeningly trying to find the cause of some of these offsets to what you expected to display. The curious thing is that some inherited or default property values are shown on the inspect tool - which leads us to assume that what is seen on inspect is all that there is . . . This change should not be too difficult to implement. And it would be a great thing to have when searching down unexpected behaviour in webpage displays.
Firefox Dev Ed is a great browser for web development and tweaking CSS. But sadly it does not always show default property values. A classic example of this is the <ul> element's default ''padding-left'' property. This apparently is set at ''40px'' automatically unless overridden by the web designer. I think that '''ALL inherited or default properties of elements ought to be clearly shown in the inspect tool's styling listings.''' You could spend hours maddeningly trying to find the cause of some of these offsets to what you expected to display. The curious thing is that '''some''' inherited or default property values are shown on the inspect tool - which leads us to assume that what is seen on inspect is all that there is . . . This change should not be too difficult to implement. And it would be a great thing to have when searching down unexpected behaviour in webpage displays.
Attached screenshots

Modified by tamjk