On Tue, Feb 28, 2012 at 1:31 PM, Rich Newpol <[email protected]> wrote: > Crap - no my error is much different (however I don't see Gusty's > patch in the git log!)
gustav can you please let us know which git commit revision it's under? > My error ends with "NameError: Name getContext not found" and it is > trying to use GWTCanvasImplDefault.py which I think is wrong... yep. actually _really_ the GWTCanvasImplIE6.py should be done properly, the implementation there is very gwt-esque. it should be done as overrides and the whole stupid "Impl" thing just nuked till it glows. > It might be a problem on my end, perhaps with my pyjd > installation....but why don't I see your patch in git yet? burble. >>> First of all, i dont understand what the first line does. and second, >>> focuswidget expects a css style string, but gets an int(?). ahh. yeah. welcome to strictness hell of the direct pyjd engines. strictly speaking, all javascript engines should also throw an error, but various browser engine implementors got so sick to the back teeth of receiving bugreports that it was *their* fault that people who don't read the fucking HTML DOM/TR specs kept shoving ints into string fields that they caved in and added, in a large number of places, "hmmm, it's an int, let's add "px" and convert it to a string". .... of course, you don't _get_ that luxury when using the engines _directly_..... .
