Support » Requests and Feedback » fr-unit still not supported?

  • Hi,

    Bringing this up once more, as previous post have been closed. The custom CSS editor still isn’t accepting the fr-unit in grid related css code. This means everytime you want to save the custom css code, you have click away the warning checkbox (meaning you have to scroll back to the top of the file), which gets rather tedious after more then a couple of times.

    It’s been years since this has been signaled, and grid is here to stay. I know I can use plugins or external ways to add and edit custom CSS (and I’m doing that when I need to implement grid code), but I still think this behaviour really should have been updated by now.

    Is there any ETA on this?

    Cheers, Raoul

    • This topic was modified 2 months, 2 weeks ago by  raoulunger.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    It looks like no one ever reported it as bug, so I’d say there’s no timeline yet.

    You can have the honor of raising the issue with the developers by following this guide: https://make.wordpress.org/core/handbook/testing/reporting-bugs/

    Hi,

    Thanks for you answer. It has been signaled on Github several times:

    https://core.trac.wordpress.org/ticket/42528
    https://github.com/CSSLint/parser-lib/issues/228

    Aparently WP makes use of something called CSSLint for the editor, but I have no idea what that is. So i’m not sure this would count as a bug, or someone responsible for CSSLint lagging (very) behind.

    Cheers

    • This reply was modified 2 months, 2 weeks ago by  raoulunger.
    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Ah, ok, I was searching specifically for fr-unit

    So, as we can see there https://core.trac.wordpress.org/ticket/42528 the problem is CSSLint, this is the third-party library we use to validate the entered CSS.

    This leaves us with two options:

    1. Get rid of CSSLint and stop validating CSS altogether. (unlikely)
    2. Wait for CSSLint to update their library to properly validate grid elements: https://github.com/CSSLint/parser-lib/issues/228

    Item 2 is most likely and it seems someone did try 9 days ago, but that was blocked for some reason: https://github.com/CSSLint/parser-lib/pull/251

    Ultimately, we’ll need to wait for CSSLint to fix this, so for now you’ll have to keep checking that warning checkbox.

    OK, thanks. I’m not very familiar with the protocols on GitHub. I see the pull request from nine days ago, but I can’t see that it’s blocked (but then again, i’m not even sure how to see that ;-).

    We’ll have to wait for CSSLint then – but I’m not sure what it is that will trigger the person or persons behind CSSLint to actually fix it.

    Cheers!

    • This reply was modified 2 months, 2 weeks ago by  raoulunger.
    • This reply was modified 2 months, 2 weeks ago by  raoulunger.
    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    I see the pull request from nine days ago, but I can’t see that it’s blocked

    The big red “Merging is blocked” at the bottom of the pull request https://github.com/CSSLint/parser-lib/pull/251 🙂

    but I’m not sure what it is that will trigger the person or persons behind CSSLint to actually fix it.

    CSSLint is built entirely by volunteers, just like WordPress, so we’ll just have to wait.

    Ah, turns out you don’t see all that information when you’re not signed in, just the pull request, but not the results. I see it now…

    We’ll wait then!

    Thanks!

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    turns out you don’t see all that information when you’re not signed in

    Ah fun, I didn’t know that! 🙂

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.