Hacker News new | past | comments | ask | show | jobs | submit login

Jake Archibald points out [1] section [2] in that page that explains it somehow. Haven't grokked it yet, but I see that popular SASS (SCSS)-BEM way of doing

    .block {
        &__element {
            &--modifier {
                p: v;
            }
        }
    }
for getting

    .block__element--modifier { p: v; }
could really be problematic from CSS parser perspective. Also in SASS `&` really is kinda placeholder and I think you can do stuff like

    .x { &+&+& { p:v; } }
to get

    .x + .x + .x { p: v; }
what again seems problematic. (But again, I don't say I've grasped that fully.)

[1] https://twitter.com/jaffathecake/status/1552200992179077126 [2] https://developer.chrome.com/blog/help-css-nesting/#:~:text=...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: