We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

"top left" in linear-gradient says "invalid property value in 56.0 new bug?

  • 2 tontu
  • 3 am na jafe-jafe bii
  • 1 view
  • i mujjee tontu mooy slowtraveler

more options

It seems that in the 56.0 the property values [top, left, bottom, right] for the first argument of the linear-gradient function do not work.

The inspector indicates an error "invalid property value" and the css is crossed out. The css is: background-image: linear-gradient( bottom right, #FF0000 43%, rgba(255, 255, 255, 0) 0% );

Substituting 315deg for the bottom right works, but is off because the div is not exactly square. I think this was introduced in the latest version because I keep up to date and it has worked for years.

It seems that in the 56.0 the property values [top, left, bottom, right] for the first argument of the linear-gradient function do not work. The inspector indicates an error "invalid property value" and the css is crossed out. The css is: background-image: linear-gradient( bottom right, #FF0000 43%, rgba(255, 255, 255, 0) 0% ); Substituting 315deg for the bottom right works, but is off because the div is not exactly square. I think this was introduced in the latest version because I keep up to date and it has worked for years.

All Replies (2)

more options

Saafara yiñ Tànn

more options

For years gradients had worked without the keyword "to" as an implied "from". Early documentation did not require the "to". "to" was suddenly required in release 56.0 (or one shortly before that) I couldn't find that change in the release notes. It would have been nice if the element inspector had a more specified error message. Thank you for the help. P.S. I could not get the second link to operate although the page came up.