jgraham

30 ms·

181.
by jgraham 13y ago
So there are a few steps here. First parser.href = url; causes the URL to be parsed. When URLs are parsed, the spec [1] says: 2. If buffer is equal to url's scheme's default port, set buffer to the empty string. 3. S
182.
by jgraham 13y ago
The WHATWG doesn't really "exist" in quite the same way that the W3C does. There isn't Process for obtaining an opinion that you can then ascribe to an organisation rather than one or more individuals. It only represents
183.
by jgraham 13y ago
There are two separate issues: 1) You can't ship your own browser engine 2) If you use the built in engine, you don't get JIT on (but Mobile Safari does)
184.
by jgraham 13y ago
It's also a total mischaracterisation of what happened here. This was not a case where someone implemented the feature and we were forced to go with they syntax for compatibility reasons. There was extensive discussion about the use
185.
by jgraham 13y ago
A standalone parser written in C is a great asset. Pretty much any language worth mentioning has C bindings, so they are now just a bindings implementation away from having a reasonably fast (the fact that performance was a non-goal notwith
186.
by jgraham 13y ago
So I agree that there is a great deal of accidental complexity associated with filing bugs, and browser developers could certainly do better here. I also see that there is a certain disconnect between the perceptions of a browser developer&
187.
by jgraham 13y ago
This is not a comment to you in particular, but when authors find bugs in browsers there are several things that they can so to ensure that the bug is fixed as quickly as possible: 1. Verify that the bug occurs in the latest available (poss
188.
by jgraham 13y ago
(and the problem preventing the bugwizard working at all should now be fixed)
189.
by jgraham 13y ago
It looks like the bugwizard hasn't been updated to make it obvious how to report mail bugs yet, but I have filed your issue.
190.
by jgraham 13y ago
Isn't it quite unfriendly to make the caller implement the main loop, and require periodic polling of the scheduler in order to run jobs? When I have implemented things like this before, I kept tuples of (time_of_next_run, job) in a heap. T
191.
by jgraham 13y ago
Even the "don't rebase once code is pushed to a shared repo" thing is more of a guideline than a hard and fast rule. For example you might reasonably want to clean up the history on branches that you have previously: * Pushed to a distribut
192.
by jgraham 14y ago
To be clear, there are two things that have historically been called "pepper". The first was a basically a better version of NPAPI, with the limited scope that implies. That was replaced by something that's basically a Google-proprietary re
193.
by jgraham 14y ago
See also: https://github.com/operasoftware/browserjs/blob/master/deskt...
194.
by jgraham 14y ago
That would work, yes.
195.
by jgraham 14y ago
The problem is that the site is using SVG paint servers to provide a gradient for the progress rect. The gradient is specified in a SVG def element with id barGradient in the HTML file. So far so good. The problem arises because the fill ru
196.
by jgraham 14y ago
The most telling thing that jQuery (or any other library) could do would be to have a policy that any browser bug workaround has to be accompanied by both a) a bug report to the browser vendor and b) a corresponding test to the relevant W3C
197.
by jgraham 14y ago
> While it's challenging to write a browser engine, it is much much more challenging to write a really fast JIT'ing javascript runtime That isn't really true. Sure, modern JITing js-engines are — arguably —the most technically advanced
198.
by jgraham 14y ago
All browsers support document.all; see [1]. It is true that Opera tried to reverse engineer more of the IE DOM than most others, for example we were the only ones to have attachEvent and friends. But in recent years that caused problems wit
199.
by jgraham 14y ago
It is important to understand that when they said "javascript" they almost certainly meant "DOM". All mainstream javascript engines, including Carakan (the current Opera javascript engine), are very compatible with the standard and with eac
200.
by jgraham 14y ago
Possibly that's very US-centric advice? I have a Kenwood stand mixer which has better specs than Kitchenaids, which historical precedent suggests will last for decades and which has a large ecosystem of available attachments (I don't know h
201.
by jgraham 14y ago
On the other hand, the world would really benefit from someone updating the libxml2 HTML parser to match the HTML(5) spec, since it has popular bindings for many other languages (e.g. lxml in python). The current implementation is broken in
202.
by jgraham 14y ago
For the record, the smallest validating document is actually: <!doctype html><title></title> Although I can't right now see the part of the spec that allows an empty title element, which is either a bug in my readi
203.
by jgraham 15y ago
If you're implementing a websocket client outside a browser, there is no need for you to follow that API spec. Feel free to invent any API that works well for the language that you're targeting. We have spent too much time in the past going