build time. Now do I have to buy a smartphone only to contribute
Mozilla? What's the next?
I actually use a Perl script to do HOTP. And there are things like
Firekey. No mobile device necessary.
Cameron Kaiser
tier-3-2-1-contact!
___
dev-pla
On 5/11/17 11:27 PM, Ehsan Akhgari wrote:
Jan de Mooij optimized Array.prototype.shit to have O(1) rather than
O(n) behavior <https://bugzilla.mozilla.org/show_bug.cgi?id=1348772>.
Wow. That's an appropriately named function. ;)
Cameron Kaiser
tier-3 port, t
being maintained.
Cameron Kaiser
tier-3, 2-1-contact
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ins, webapprt), and I don't
know how much of a change would invalidate the use of the trademark.
Also (likely when Electrolysis becomes mandatory), we'll have to fork
one day anyway when certain dependencies mean it becomes no longer
buildable, so this way the branding can come
ure Tier-3 platforms and it would
definitely bust TenFourFox (we can't even get clang to be happy on 10.4
currently). Not that we haven't been on borrowed time for awhile; I just
point it out for the record.
Cameron Kaiser
___
dev-platform maili
ot of people upset.
Not an issue since initial rollout to beta and release will be to users who do
not have addons installed.
Assuming e10s is not enabled for release 45, will it also remain not
enabled on 45ESR?
Cameron Kaiser
___
dev-platform ma
On 12/13/15 12:50 AM, Nicholas Nethercote wrote:
On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote:
This would essentially mandate, then, that Gecko can only be built on
platforms with a Rust toolchain. That may be desirable, but it would
probably bust some of the obscure Tier-3 platforms
there.
On 12/14/15 2:22 PM, Nathan Froyd wrote:
> On Sat, Dec 12, 2015 at 5:17 PM, Cameron Kaiser
> wrote:
>
>> This would essentially mandate, then, that Gecko can only be built on
>> platforms with a Rust toolchain. That may be desirable, but it would
>> probably bust
On 12/14/15 7:36 PM, Gregory Szorc wrote:
On Mon, Dec 14, 2015 at 6:58 PM, Cameron Kaiser
wrote:
That said, I kind of object to the fact that no one brought this up until
I noticed it in passing, and the work to get Rust up on a tier-3 platform
-- a language that currently has no relevance to
Ref aIID);
Interesting. How does your code work in practice?
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e protocol handler component, or is there some other problem? A
cursory search of MDN was no help.
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 1/4/16 12:09 PM, Dave Townsend wrote:
On Mon, Jan 4, 2016 at 12:03 PM, Cameron Kaiser wrote:
What's different about nsIProtocolHandler in e10s? OverbiteFF works in 45
aurora without e10s on, but fails to recognize the protocol it defines with
e10s enabled. There's no explanation
d finishes transferring data, does it or the parent have to
do anything else special?
Hopefully this will
get you started, along with this inspirational gopher:// video:
https://www.youtube.com/watch?v=WaSUyYSQie8
:)
It's in the hole!
Cameron Kaiser
rs and setters for the load group and notification callbacks, and
uses the thread manager to get the current thread to use as an event
sink for the socket. Would all this work in the child process?
Cameron Kaiser
___
dev-platform mailing list
dev-p
On 1/5/16 1:31 AM, Gijs Kruitbosch wrote:
On 04/01/2016 20:03, Cameron Kaiser wrote:
What's different about nsIProtocolHandler in e10s? OverbiteFF works in
45 aurora without e10s on, but fails to recognize the protocol it
defines with e10s enabled. There's no explanation of this in t
a bit more of a hassle.
TenFourFox does not (we use in-tree NSPR, with our patches overlaid).
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
atter, I can't combine the two. What's the best combination
of flags to get this to work as it did in previous versions? It used to
work just fine with just ALLOWS_PROXY | ALLOWS_PROXY_HTTP |
URL_IS_LOADABLE_BY_ANYONE.
Or, can I use resource:
On 1/25/16 9:49 PM, Boris Zbarsky wrote:
On 1/26/16 12:42 AM, Cameron Kaiser wrote:
Currently, it sets ALLOWS_PROXY | ALLOWS_PROXY_HTTP |
URI_IS_LOADABLE_BY_ANYONE | URI_IS_UI_RESOURCE.
Those last two flags are defined to be mutually exclusive; setting both
has undefined behavior in the sense
On 1/25/16 9:49 PM, Boris Zbarsky wrote:
On 1/26/16 12:42 AM, Cameron Kaiser wrote:
Currently, it sets ALLOWS_PROXY | ALLOWS_PROXY_HTTP |
URI_IS_LOADABLE_BY_ANYONE | URI_IS_UI_RESOURCE.
Those last two flags are defined to be mutually exclusive; setting both
has undefined behavior in the sense
r. I don't think that's
necessarily true since most Steam titles have substantially higher
system requirements.
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ave to take to bring Rust up
from scratch on a new platform?
Cameron Kaiser
tier-3s in rain dept.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
comparison for testing, so doing so has benefits beyond just getting
Tier-3 or unsupported systems functional.
Cameron Kaiser
ein guter Tier-3kenner
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
that handles
2FA HOTP. The algorithm is very easy to implement and there are lots of
desktop choices too.
Cameron Kaiser
tier-3 misery and company dept.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
, especially for searching
historical source trees.
Cameron Kaiser
mxr? I dn't evn knw hr
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
rt.
I'll bet some extensions implement custom protocol handlers that do the
same thing. (In fact, I'm sure of at least one; OverbiteFF uses null
host names to denote pseudo URLs internal to the protocol handler.) This
might be considered gauche, but probabl
al, but as I have no relations to the team
doing that, I could be wrong.
Dave Yeo would be the right person to ask, since his name is over most
of m.dev.ports.os2 (dave.r.yeo AT gmail).
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lis
not, but I want to make sure.
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
at the taste of the user. Maybe suggestions
for an automated means would be nice, but a determined user will want to
strip things out in just the way they would like, and I think they
should have the opportunity to do so. There's nothing that says this has
to be one or the oth
On 3/28/14 6:12 AM, Neil wrote:
Cameron Kaiser wrote:
For TenFourFox, I've often toyed with implementing switches for
box-shadow, blur, etc., so that people on the very low end of the spec
(we still support G3 Macintoshes) can turn these rather expensive
features off. I'd rather do
ce to open sockets, and I'm sure it's not the
only one that does. The implementation is non-blocking, but I want to
clarify from the above post that the intention is not to block non-Necko
consumers from using it. Is this acceptable usage, or is it deprecat
, but I mostly use it for profiling entire
processes rather than the specific profiling *control* the Shark code
facilitates. If it turned out to be a big deal, it could always be added
back in our local changesets since there's really not that many sections.
Cameron K
, and not because I still run such a site, I've always found
Gopher to be a better fit for resource-constrained computing. The
Commodore 128 sitting next to me does very well for that because the
protocol and menu parsing conventions are incredibly trivial.
What is your 10MHz 8-bit system
On 4/14/15 3:47 PM, commodorej...@gmail.com wrote:
On Tuesday, April 14, 2015 at 2:51:32 PM UTC-7, Cameron Kaiser wrote:
Candidly, and not because I still run such a site, I've always found
Gopher to be a better fit for resource-constrained computing. The
Commodore 128 sitting next to me
..
So, Gopher then.
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
xits in this fashion, but to get
around a linker issue.)
Cameron Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ite a
difference across the spectrum.
But even where this feature doesn't exist (post-Netburst x86, most
ARM), it is my understanding that it will still cause code generation
to "favour" the likely branch such as making it more likely to stay in
the I-cache, etc.
Cameron Kaise
36 matches
Mail list logo
