So, I’m a thirtysomething mechanical engineer and lousy guitarist. I work in the semiconductor industry, spend most of my spare time developing for the web, and own quite a few affordable (!) electric guitars, a handful of Raspberry Pis, and a couple hacked together MAME—I know—cabinets. Also, happily married, father of two, wannabe investor.
If something is mostly confusing, you may not need it. Also, lots of “tech bloggers” are so obsessed with trying every latest web technology that they’re constantly breaking their own URLs and feeds.
In other words, `span:nth-child(3)` does _not_ simply select the 3rd `span`!
I think this is _exactly_ what happens. A `span:nth-child(3)` selector will match only the `span` that is also its parent’s 3rd child. Your `br` isn’t counted as a span, it’s counted as a child element.
> But today I learned that :nth-child() counts all elements[.]
I know that doesn’t actually help a whole lot, but think about it for a second.
Would love to see this fixed, or rather, have the ability to easily extend WordPress’s inline link modal to accept class names. We don’t need “IndieWeb blocks,” after all. HTML classes suffice; the “Post Type Discovery” algo will take it from there.
The one that’s probably most relevant: https://github.com/WordPress/gutenberg/issues/27345
Bookmarking this, on MySQL querying by physical distance. (My original goal for the geekcompass.com domain was to host a sort of “Tripadvisor for nerds.”)
I mean, I already use a filter/action hooks package rather than Laravel’s built-in events/model observers. Might as well go all the way.
Some these add new columns to existing (entries, feeds) tables, which obviously results in a lot of NULLs. Might not be an issue per se, but I was looking into separate tables + somehow adding the necessary LEFT JOINs in (like, by making all queries filterable or something). Could simply use a Custom Fields/Meta package, too (there’s several for Laravel).
Folks have been wanting a way to easily extend these links forever—three years, at least; there’s several GitHub issues—so not gonna get my hopes up. I did, however, just implement a different approach, where I add, e.g., a `u-bookmark-of` class to a _paragraph_ block, and a `the_content` filter then _removes_ that class and adds it to that paragraph’s first _link_ instead. Hacky, but probably more robust than “Edit as HTML.”
Found some more code examples and am now able to either add a new formatting button that will trigger a completely inaccessible “href” popover but otherwise sorta works, or replace the core link button with something that, uh, will add an `a` tag with a class. But I’m a React noob. Plus, _all_ we need is for core links to accept a class.
(Thing is, you can “Edit as HTML,” but switching back to the [visual] link editor will remove your manually added attributes.)
I’d much prefer this over a custom block (or some kind of meta box approach), as I want to be able to add such links anywhere in a post’s content.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!