David Keijser

sure, I never used the codecs module much but that sounds like a reasonable feature. A PR adding this is most welcome :)

The exact separation of the threads is not clear to me and maybe it something we would have to untangle when we get to that. But even then I think...

sry. g_task_run_in_thread was not the one I was thinking of. By I think I remember reading you could attach them to specific main loops

hmm, ok. so page like it's implemented now doesn't actually work then? I forget what is just placeholders :) To get the extension working as big task on it's own...

Re variables it's very tempting to run it with the gui because of all the gobject properties we are setting. But I think conceptually it belongs in the uzbl thread...

Looks like this behaviour made it into the tests too

I'm guessing your talking about elements that use javascript click events? The really is not reliable way of figuring out if an element has javascript click handler. Simple inline onclicks...

it's loading a script on page load that defines the functions. this will always happen before the page is complete. The function is then run when you press the keycmd...

Hmm. I can't reproduce this. There was a issue with clearing special keys that was fixed after 0.9 which I guess could be related. Would you mind giving building from...

With webkit1 being deprecated in all major distros it could be argued that next is in practice more stable at this point. There's still much to be fixed for webkit2...