yeah... those changes, per comments, were not reflected this direction, which is unfortunate to say the least.
at any rate, as i said in the pull req, the whole "match user-agent" thing is-and-has-always-been incredibly fragile (esp. considering the myriad of mobile OSes, browsers, etc these days) and needs reworking. ie6 is no longer a consideration, but the code base is still a bit out-of-date regarding that... a solid long-term solution is to rapidly feature-detect on bootstrap, then selectively polyfill/patch/alias the browser's native API into a uniform API the translator can target, virtually eliminating the original need for overrides altogether. other ideas on this front are certainly welcome. however, just yesterday, i realized how to achieve 100% out-of-the-box support for the gobject realtime bindings (!), *despite* the lack of support in gobject-introspection (use cytpes manually! of course! it's so simple!) so i'm currently working to push that out, followed by *gasp* a real release, but these problems you've encountered are definitely a high priority, albeit as part of a larger architecture issue... alas, in the interim, should further changes be necessary to support newer IE releases, feel free to open more requests. -- --- You received this message because you are subscribed to the Google Groups "Pyjs.org Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
