The more time I spend with #Javascript Framework code, the more I am convinced the devolution and/or dislike of the #CSS Cascade makes sense. Whether it's building an entire application interface or a standalone app or a one-size "responsive" plug n' play app/site I'm seeing why.

Jun 8, 2020 · 11:13 PM UTC

2
5
7
If one views source derived from a #Javascript #Framework and opens a current in-browser dev tool, the #CSS is a godawful confusing mess! It is logical to just want to override conflicts in style with inline styles and/or !important. Educators may be looking at it backward. Me.
1
3
Instead of explaining the browser sort first, if we start with the most specific rule (Specificity algorithm) we end up with an actual #CSS rule that regardless of origin will apply given we follow (I'm almost sure) likely no more than 3 steps and two exceptions empowering devs.
2
3
The conclusion to this theory of how to tap back into the power of the cascade results in far less #CSS far less confusion far more elegant code and far less obfuscation. It also reveals that our tools have become part of that obfuscation and resulted in over complex processes.
3
Replying to @mholzschlag
You’re reminding me I’ve got to get off my butt and start getting a site built for my lodge. I feel old and rusty right now, so I’ve been delaying it. I was planning on plain HTML and CSS with minimal JavaScript. The target audience is much older and not as tech savvy.
1
1
The open web stack does what it is meant to. do when applied logically. That's a logical approach, not old and rusty providing good #a11y is in play at all times. HTML forms have come up a lot as others point out as being huge fail spots in accessibilty audits.
1
2
more replies