ConvoBreaker

@Not-The-Conversation-Starter

Untitled

Some/Guy

Trillions are dead and you complain about me not having a title.

Explore this dead website through my blog! I have good taste! I swear!

Tumblr

www.tumblr.com/not-the-conversation-starter

Bluesky

convobreaker.bsky.social

ConvoBreaker @Not-The-Conversation-Starter9/24/2024, 10:25 AM

ruby @srxl

ruby @srxl9/6/2024, 10:08 PM

click the lever!

oops, it's stuck...

Now you're thinking with

Now you're thinking with portals!

#css crimes #portals

You must log in to comment.

in reply to @srxl's post:

ruby @srxl9/6/2024, 10:10 PM

you'll want https://cohost.org/srxl/post/7570554-details-open-name on the same page for this to work

best viewed on desktop, firefox requires latest stable version (130)

Ξ @exerian9/7/2024, 3:27 AM

it worked but "with" wrapped to the second line instead of going into the portal. the "with" on the blue portal did show up correctly.

ruby @srxl9/7/2024, 4:04 AM

there's probably a solution to this but my brain didnt have it last night when i hacked this up

Ξ @exerian9/7/2024, 4:09 AM

white-space: nowrap; would almost certainly do it.

ruby @srxl9/7/2024, 5:37 AM

needed a flex-shrink: 0 on the portal as well to stop it from getting squished but you're right. totally forgot that property existed. should look better on mobile devices now, cheers!

sage @wavebeem9/6/2024, 10:10 PM

oh jeez, i wonder if/when they'll do something to sanitize "name" to not collide across posts lmao

ruby @srxl9/6/2024, 10:19 PM

i haven't been able to think of anything harmful you can do with this but it certainly doesn't feel like it should work lmao

sage @wavebeem9/6/2024, 10:24 PM

true but i always err on the side of "someone will figure out how to make me regret leaving this feature in there" because security researchers are built different lmao

dragongirlsnout @minecraft9/6/2024, 10:56 PM

it could potentially be an issue if there were native ui components using a named <details> element

sage @wavebeem9/6/2024, 11:03 PM

yeahhhh but only if opening/closing those was a problem... otherwise it's just annoying :eggbug-nervous:

ruby @srxl9/6/2024, 11:17 PM

the UI element would have to be open by default, AND the post would have to come before it in the DOM (iirc? might be wrong on this) - if both of those cases aren't met, then the post will need to be interacted with to have any effect on the UI

OH and the name attribute's value gets a user-content- prefix when posted so it probably can't touch UI anyway