Steven Parkes
Not a member
Steven Parkes's latest activity
Sunday, March 28 2010
-
Steven Parkes commented at 4:33 PMI tend to agree with the external/platform object as a switch point. I'd actually prefer to derive (in the javascript sense) the platform object from the base v...
Saturday, March 27 2010
-
Steven Parkes commented at 5:01 AMTouch events make as much sense as mouse events. A headless browser has no less of a touch interface than it does of a mouse interface.
I'll end up doing this a...
Friday, March 26 2010
-
Steven Parkes commented at 3:36 AMWe could up load the release artifacts to the downloads area of github. Then all we need a commit hook that looks for tags and does it automatically.
Sunday, March 21 2010
-
- Tag cleared.
Can you try changing the wait() to wait(-1)?
This got changed very early in the refactor, so there's no history in git. I'm not sure if there was a problem that...
Friday, March 19 2010
-
Steven Parkes commented at 2:32 PMYeah, I know there's a URI spec. And there's also a URL spec. I was misremembering: it's not that there's isn't a spec for file URLs: that's actually described ...
-
Steven Parkes commented at 1:44 PMPretty cool ... and a lot of the plumbing.
I have to admit, I've never been crazy about the Python API for this, though. Just breaking things down to a tuple .....
-
Steven Parkes commented at 1:08 PMI haven't used the Python url stuff in a while. (Obviously) the Ruby port uses the Ruby classes. They've got some really nice features. They'll do url_a + url_b...
-
Steven Parkes commented at 8:14 AMRather than doing the indexof stuff, just using a uri parse on the path? Then you can just look at the scheme and see if it's javascript or about?
Monday, March 15 2010
-
Steven Parkes commented at 1:11 PMThere's code that makes the parser sync to handle innerHTML, which can't have script tags and so can't do document.write.
As far as I know, there's no way to se...
-
Steven Parkes commented at 1:05 PMThe parsing is not complete at the end of the parseDocument precisely because the parser is async, which is why the wait is there. The parsing is taking 480 ms.