On Wednesday, April 8, 2015 at 8:03:45 PM UTC-4, L. David Baron wrote:
This is a specification that's the W3C version of a piece of the
WHATWG HTML specification. It appears (from looking at code) to be
something we implement, although I'm not sure if there are
differences between the W3C
At this point the HTTP/2 ship has sailed. It's exceedingly unlikely that
we or any other browser vendor or the IETF are going to pivot to a modified
HTTP/1.1 to get the feature set here.
Sorry!
Jason
On Thu, Apr 9, 2015 at 11:53 AM, Daniel Stenberg dan...@haxx.se wrote:
On Wed, 8 Apr 2015,
On 2015/04/09 16:41, Ms2ger wrote:
What are other browsers planning to do?
Not sure. We're the first implementer around new KeyboardEvent.
Do we have any tests in wpt that could show interop?
I think, no. I don't know if tests of DOM Level 3 Events are included in
wpt. (of course,
On Wed, 8 Apr 2015, max.bruc...@gmail.com wrote:
A request begins by adding a header: X-Req-ID, set to a connection-unique
value. The server responded with an exact copy of this ID, and a
X-Req-Target header which specifies the location of the response(for server
pushing mostly). The server
On 9 Apr 2015, at 15:24, Andrew Halberstadt ahalberst...@mozilla.com wrote:
Bug 1046992 (just landed on inbound) removes the `mochitest-remote` and
`mochitest-b2g-desktop` mach commands.
Instead, simply run |mach mochitest-plain| like you would on desktop. The
`mochitest-plain` command
Just thinking, but what if each profile remembered what channel it was
meant for? When using a profile in a different channel, you would have
an option to create a backup of the profile. If you were going forward,
you would get a simple notification that your profile's channel was
being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/09/2015 03:27 AM, Masayuki Nakano wrote:
EventModifierInit is a dictionary to initialize modifier state at
creating untrusted event. This allows to initialize AltGraph,
CapsLock, Fn, FnLock, Hyper, NumLock, OS,
ScrollLock, Super, Symbol
On Thu, Apr 9, 2015 at 12:11 PM, Jason Duell jdu...@mozilla.com wrote:
At this point the HTTP/2 ship has sailed. It's exceedingly unlikely that
we or any other browser vendor or the IETF are going to pivot to a modified
HTTP/1.1 to get the feature set here.
Oh, I don't know... If someone can
The functionality provided by nsINSSCertCache has been redundant for a
while now. To prevent potential confusion, it has been removed[0][1]. If
you ever needed to do something like this (to get a list of all known
certificates, for example) :
let certcache =
Bug 1046992 (just landed on inbound) removes the `mochitest-remote` and
`mochitest-b2g-desktop` mach commands.
Instead, simply run |mach mochitest-plain| like you would on desktop.
The `mochitest-plain` command will detect what platform you have built
and do the right thing.
In the near
10 matches
Mail list logo
