Settings window is merely builtin (embedded) browser with the only one pebble-specific thing - there is a handler for uri scheme "pebble://" with authority "close".

At the moment embedded browser is WebKit2 based, so if creating some interface need to consider its limitations.

If something is not working as expected - well, can't help much except one thing - I'm trying to bring embedded geko engine instead of builtin webkit. not sure though when and if it is going to happen.