Thanks for your reply.
> * it's not clear to me that starting with a separate crate makes sense.
> It might be less work to prototype all of it inside Servo first.
The prototyping inside servo can definitely be done without a separate crate
but if servo "ports" like glutin want to provide rich
I'm glad someone is thinking about how to improve Servo's current
minimal keyboard input. I have a few thoughts:
* it's not clear to me that starting with a separate crate makes sense.
It might be less work to prototype all of it inside Servo first.
* what is the benefit to glutin if it share
Hi,
I'd like to improve Servos keyboard support.
At the moment Servo assumes everyone uses US-keyboards and allows only
entering ASCII characters in forms. While KeyboardEvents are supported
they are not created for keys present on international keyboards.
Servo should try to conform to the K
3 matches
Mail list logo
