David Herman

User reported missing: https://developer.mozilla.org/en-US/docs/Web/CSS/text-overflow

Probably a first pass (or maybe even the only thing required to close this bug?) is to let users edit their body html in the kobweb block (which currently only...

Hey Rafael, sure that would be great! No pressure. You can also ask questions here -- it's been a while since I filed this so can't really remember if there...

Ah I didn't realize I was talking to someone who is already working on a Kobweb project and already had something working locally. Nice! While I am a huge fan...

Probably worth looking at Compose Navigation as well: https://developer.android.com/jetpack/compose/navigation in case there's anything worth borrowing from their approach

I'm still on the fence whether this feature is worth doing or not. You're right that external URLs would be raw strings anyway. The main benefit I could see is...

It would also be possible to do something like this: ``` interface Route { fun toRouteString() } fun Link(path: String, text: String) // Already exists fun Link(route: Route, text: String)...

Don't forget updating the .gitignore files inside the templates!

Note: Marked this with 1.1 because it shouldn't block a 1.0 release, but solving this in the 1.0 timeframe might still be a killer feature for users.

Note from another user: > Would be great for kobweb to have the isinviewport functionality, based on the intersectionobserver api instead probably > Also you asked earlier about the IntersectionObserver...