PSA if you do #webdev, MDN isn't accurate in representing Chrome's support (well, lack thereof) for margin/padding block and inline. Had to deal with this when working on the @streambits website and currently on #Collea.
@streambits Using block and inline (margin-inline or margin-inline-start, as examples) can greatly simplify support for RTL as well ideographic languages (which can be written LTR or top to bottom), so I was quite surprised when I saw that Chrome lacked support given how diverse Google is.
@streambits So what you end up with is a situation where you'll need / want to use HTML Element dir attribute specific styling, :dir where supported, direction specific margin and padding, and margin / padding block / inline where supported. Just so you're not alienating a bunch of people.
@JoshStrobl Actually, you should go and give a TED talk. 😂 I could really learn a few things from you. By the way, what is your primary web browser?
@JoshStrobl Oh.... Yeah! I prefer Firefox too. For me, I like it because it is much more secure than most. Do you use the Facebook container too? I don't really have a use for that extension since I am not on Facebook. 😉
@sudo Nah, I haven't felt the need to use it since I have a "Personal" container and uBlock Origin anyways.
@JoshStrobl Is your 'enhanced tracking protection' set to 'strict' too?
@sudo Nah, it's set to standard otherwise it tends to break content embeds.
Everyone is welcome as long as you follow our code of conduct! Thank you. Mastodon.cloud is maintained by Sujitech, LLC.