It is the true teacher who leaves the class knowing they have learned the most.
Tucson, AZ
Joined September 2006
- Tweets 64,757
- Following 13,801
- Followers 26,057
- Likes 36,165
Error correction to previous post: Montagu published that book in 1948. I have no idea why 2001 is what I typed. That said, he spent his latter years in New Jersey. Sadly was blacklisted during McCarthy era. As I type I wonder how many folks don't know or don't care. :Pin drops:
The idea of "race" represents one of the most dangerous myths of our time.
- Ashley Montagu, Anthropologist, from his book "Man's Most Dangerous Myth: The Fallacy of Race” 2001.
Fascinating man. And epically quotable.
en.wikipedia.org/wiki/Ashley…
#race #mythology #ThinkAboutThings
1
4
Hi there! How are you? Serious medically but stable and happier with myself and life. I was on a terrible medication I shouldn't have ever been given and off it I have relief. Bone Marrow Aplasia at my age and situation is incurable and causes multiple systems to fail with time.
1
1
'Specificity First Style' Step 4.
PRESENCE OR ABSENCE OF !Important
If present, why? Will steps 1-3 resolve? !Important should balance power between user and author styles only.
#CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking
1
1
2
'Specificity First Style' Step 3.
PRESENCE OR ABSENCE OF INLINE STYLES
If present, why? Will step 1 or 2 eliminate or require inline style to achieve the most specific rule.
#CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking
1
1
1
'Specificity First Style' Step 2.
RULE. ORDER
This is where we (not our tools) examine all rule order and correct where a conflict or override due to calculation results is found.
#CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking
1
1
1
'Specificity First Style' Step 1.
ORIGIN
Where we (not our tools) know our style rules are including all sheet types, inherited style, global style, undefined style.
#CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking
1
1
1
Assuming knowledge of how to write style rules, what style sheet types exist, and setting aside components for this portion, I see 4 areas of #CSS where we may find insight into refind authorship.
I encourage #Javascript and framework devs to er, react. You have keys I don't. OK
2
7
7
Me too. Freemason eh? I know quite a few! A site like that screams for open web stack, minimal JS. It's purpose is very OG Web. AKA not an app. :D
1
1
The component issue my ever challenging friend and colleague Sneds points to is a huge #CSS concern. I believe it's ok so long as we learn why this tech for a specific result. When. Where. Why. Such choices take skills, experience, leadership, vision and education. And many cats.
Some of this I think is still trying to figure out what we're doing (as the web dev community at large) with styling components, and having isolated styles for them. Many of the problems of specificity are about compartmentalising components, as far as I see?
1
Thank you. I am always learning and often wrong, or not the best at process for all as one size just...doesn't ;-) I do think deeply and study hard because I know there's as much power in Web for good due to huge adoption and reach. We are in a dark night. Which precedes dawn.
1
1
Hey Sneds! Yes, the component issue is a big part of isolating styles. My thought is that can be even more powerful when applied well and of course: WHEN AND WHERE. One component does not fit all needs, and so on. So yes, very much a need to address, I agree my dearest YOU! xo/m
Which Framework? Mostly #ReactJS as it's prevalent but I study/examine others, CMSs and related too from the POV of systems and process engineering, in this case.
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
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
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
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