Question: why an external DTD is accessed (or not)? (svg11.dtd)

Hi, I have been puzzled at a pair of strange warning messages over the last few years, but can't hold the curiosity any longer. So here is my question. During the invocation of TB |make mozmill| test suite by running locally produced DEBUG version of C-C test, I have seen the following

Re: Question: why an external DTD is accessed (or not)? (svg11.dtd)

Bug 994305 is on file for this. - Kyle On Sat, Nov 21, 2015 at 10:57 AM, ISHIKAWA,chiaki wrote: > Hi, > > I have been puzzled at a pair of strange warning messages over the last few > years, but can't hold the curiosity any longer. > > So here is my question. > > During

Re: Question: why an external DTD is accessed (or not)? (svg11.dtd)

Thank you for the clarification. It is assuring to know that some people are aware of the issue. On 2015/11/22 3:59, Kyle Huey wrote: Bug 994305 is on file for this. - Kyle On Sat, Nov 21, 2015 at 10:57 AM, ISHIKAWA,chiaki wrote: Hi, I have been puzzled at a pair

Question: "Chrome file doesn't exist: ..." in |make mozmill| log by running DEBUG versions of C-C TB

Here is another question of mine that has bothered me for a long time. During the invocation of TB |make mozmill| test suite by running locally produced DEBUG version of C-C test, I have seen the following WARNING messages in the log regarding "Chrome file doesn't exist". I checked the

Re: Merging comm-central into mozilla-central

After reading this whole long thread (though I daresay I've read some parts of it "diagonally") I learned in it that the official MoCo policy is that Firefox developers must NEVER spend time (or at least company time) on giving the least help to Thunderbird and SeaMonkey. This made me sad but

Re: Is that possible to implement Sqlite.jsm with ctypes so that is can works in the worker?

On 20/11/2015 19:51, Till Schneidereit wrote: > On Fri, Nov 20, 2015 at 12:23 PM, David Rajchenbach-Teller < > dtel...@mozilla.com> wrote: > >> It could be improved a bit, but the real issue is that JavaScript is a >> high-level, garbage-collected, dynamic programming language, while C is >> a