Robert O'Callahan wrote:
WM_MOUSEMOVE events, like other native events, would still take priority over
all Gecko events and potentially starve the refresh driver.
Sorry, I misread the code, I didn't realise that it only prioritised
keyboard and mouse events over other native events.
--
Wa
On Sunday, February 24, 2013 4:27:16 AM UTC+1, Brian Smith wrote:
> I notice that your company has developed a cross-browser framework for
> building extensions. That means you are probably familiar with Chromium's
> requirements here. I believe that Chromium requires you to do things the same
>
The daily build of xulrunner runtime for mac in the unstable trunk (21a and
22a) are broken (only 46 bytes). Any idea what the problem is?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 2/24/13 12:44 PM, matt...@salsitasoft.com wrote:
Unfortunately I'm relying on DOMWindowCreated to inject my symbols into the
window, and this is no longer fired in FF19 with the type set to chrome.
Uh code inspection and basic testing over here suggest it fires just
fine, for what it's
On 2/23/13 1:08 PM, matt...@salsitasoft.com wrote:
Currently I have to admit that I don't understand how the code addresses the
issue of giving content access to the responseXML DOM returned by the
Cc['@mozilla.org/xmlextras/xmlhttprequest;1'].
The DOM returned by responseXML is associated wi
5 matches
Mail list logo
