Hello, and apologies if this is a duplicate thread. I tried to subscribe to the list via web and then initially emailed it from the wrong address. I've been doing some experiments to see if I can integrate Dillo with macOS a bit better. Here's a short video demonstrating a proof of concept of some basic changes, just using the native window toolbar and menu instead of the FLTK NavBar: https://mastodon.gamedev.place/@irskep/115501294400482061 I'd be happy to redo this work to a higher standard and submit a proper patch. But before I do that, I wanted to ask, is this sort of change in line with the direction of the project? Are you interested in deeper system integrations, or do you prefer to maintain an entirely cross-platform codebase and rely just on FLTK? The code for my prototype is here, just to get a sense of what's needed: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments The primary needs for platform affordances fall into two buckets: message passing, and customization. For message passing, some UI state would need to be communicated out to the platform-specific code, stuff like whether back/forward buttons should be enabled, or which tab is currently active. I wanted to tweak the window title to add a tab count, so I added that as well. Those types of changes are here: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments#diff-0... For customization, I'm referring to things like not showing the FLTK-based NavBar if its controls are being shown elsewhere in the UI. Those types of changes are here: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments#diff-c... Let me know how you'd like me to proceed or if this outside the scope of what you want to have in the codebase. I want to be a help and not a burden! Thanks, Steve