I would prefer not to do this, as this undoes the change we made when making servoshell (converting a port into the default minibrowser). Instead if there are things that should be part of the servo API, they should be moved gradually into libservo.

@mrobinson I'm fine not to add this for now, but we still need to iterate the current servo shell (or servo itself) that can draw its own chrome in the end. Is it okay to bring winit code to libservo later on? Because I believe you mentioned we don't want another port with duplicated code already.

For reference, chromium does have different frameworks like aura and ozone for windowing to different platforms.