On 10/8/13 10:32 PM, Justin Dolske wrote:
Would that be a kungFuDeathGrep? (Sorry. Just making weak pun.)
You mean mozilla::WeakpPunT?
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
On 10/02/2013 12:33 PM, Erik Rose wrote:
What features do you most use in MXR and DXR?
(Apologies for the late reply; didn't really check newsgroups during the
summit - bad wifi and having too much to do. Didn't about the design
session in SC for the same reason.)
I look up XPCOM interfaces
On 10/02/2013 06:06 PM, Botond Ballo wrote:
Having to repeat 'expr' is rather unfortunate, and C++14
fixes that. You can now write:
auto function(A a, B b)
{
return expr;
}
The only restriction is
that if there are multiple return
On Wed, Oct 9, 2013 at 1:49 AM, Neil n...@parkwaycc.co.uk wrote:
Nor can I seem to get regexp search to work; I never get any results.
If you're using the regexp field in the advanced search, you're
probably failing to put '/' (or some other delimiter) at the start and
end. I too was having
Nicholas Nethercote wrote:
On Wed, Oct 9, 2013 at 1:49 AM, Neil n...@parkwaycc.co.uk wrote:
Nor can I seem to get regexp search to work; I never get any results.
If you're using the regexp field in the advanced search, you're probably
failing to put '/' (or some other delimiter) at
On Wednesday, January 9, 2013 12:17:12 PM UTC-5, joshu...@gmail.com wrote:
I know that there are probably well thought out reasons that this isn't a
features already...BUT! Lot's of US Government users can't use Firefox
because it doesn't use the Windows certificate store.
Months late to
Better python support. For example, the function name parameter doesn't
work with ext: .py
http://dxr.mozilla.org/mozilla-central/search?q=function%3Astart%20ext%3A.py
-- no results
http://dxr.mozilla.org/mozilla-central/search?q=%22def%20start%22%20ext%3A.py
-- results
On 10/02/2013
Attack surface reduction works:
http://blog.gerv.net/2013/10/attack-surface-reduction-works/
Removing E4X broke the NSA's EGOTISTICALGOAT attack - a type confusion
vulnerability in E4X.
In the spirit of learning from this, what's next on the chopping block?
A quick survey of the security-group
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
* XSLT (Chrome have already announced they will remove it:
We'd need to do the same extension thing they're proposing or something;
this is used in the wild for sites
On 10/9/2013 12:18 PM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
I'm all for this, although the risk is probably quite small because we
don't expose RDF to content.
--BDS
On 10/8/13 4:27 PM, David Rajchenbach-Teller wrote:
That sounds quite sufficient for me.
Do we have plans to backport Cu.import to ES6 modules?
No plans yet. Want to work on it with us? We're not ready to start just
now, but parser support for ES6 modules is being added, and the
self-hosted
On Wed, Oct 9, 2013 at 9:01 AM, Gervase Markham g...@mozilla.org wrote:
* Windows integrated auth
I would love to kill Windows integrated auth. It seems like doing so
would mean almost the same thing as saying we don't care about
intranets though. That's something I would be very interested in
On 09.10.2013 18:01, Gervase Markham wrote:
* XSLT (Chrome have already announced they will remove it:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zIg2KC7PyH0
;
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/k8aIeI6BCG0
CON to remove XSLT support from
On 10/9/13 9:49 AM, Benjamin Smedberg wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
I'm all for this, although the risk is probably quite small because we
don't expose RDF to content.
Bug 833098 - Kick RDF out of Firefox
Comments in the bug suggest a
On 9/10/13 17:18, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
* XSLT (Chrome have already announced they will remove it:
Have they? I admit I haven't made it through every post in their
discussion
On 2013-10-09 12:18 PM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
We use RDF in Firefox, in localstore.rdf among others I guess.
* XSLT (Chrome have already announced they will remove it:
On 2013-10-09 12:01 PM, Gervase Markham wrote:
* Editor (share a JS implementation with Servo instead)
I've been fantacizing about this for a while (not about the Servo code
sharing part per se of course.) This is hard because of a variety of
reasons, including the fact that there is no
On 10/9/13 2:25 PM, Ehsan Akhgari wrote:
On 2013-10-09 12:18 PM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
We use RDF in Firefox, in localstore.rdf among others I guess.
Right. We should
Gervase Markham wrote:
* XSLT
Doesn't the XML prettyprinter use XSLT?
--
Warning: May contain traces of nuts.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Gervase Markham wrote:
* Editor (share a JS implementation with Servo instead)
By the time the editor works in Servo, you probably want to think about
reducing your attack surface by switching to Servo instead.
--
Warning: May contain traces of nuts.
On 10/9/13 11:29 AM, Boris Zbarsky wrote:
RDF
We use RDF in Firefox, in localstore.rdf among others I guess.
Right. We should stop doing that. ;)
Bug 559505 - localstore.rdf kills ponies
I got hung up on the (ancient) patch there because RDF is baked pretty
firmly into the XUL Tree
Hi All:
I hope everyone had a chance to see Shumway on the big screen at the Summit.
I'm very proud of what the Shumway team has accomplished to date. While the
demos looked amazing, we've got quite a bit to do to get Shumway to a
product-ready state. In particular, the user experience on
On 10/9/2013 2:25 PM, Ehsan Akhgari wrote:
On 2013-10-09 12:18 PM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
We use RDF in Firefox, in localstore.rdf among others I guess.
This is not that
During the Thursday, October 17th meeting, we will have guest stars Mary
Trombley and IIana Segall from User Research joining us to share their findings
from the Flash CTP research project they conducted earlier this year.
(I'll send out a reminder next week).
Erin
On Oct 9, 2013, at 12:05
On Wed, Oct 9, 2013 at 9:01 AM, Gervase Markham g...@mozilla.org wrote:
Attack surface reduction works:
http://blog.gerv.net/2013/10/attack-surface-reduction-works/
In the spirit of learning from this, what's next on the chopping block?
Master password. The UI is prone to phishing, it causes
On 10/9/13 6:18 PM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
Yes.
I think that localstore.rdf is the long pole. Not so much because we
abuse it for xul persistance, that's OK to fix. The
Release Engineering is migrating the Windows 64-bit _build_ machines to
a new, managed machine image which will decrease the amount of
administrative overhead needed to deploy new instances, make image
changes, etc.
It uses the same build toolchain as the current Windows 64-bit images
(MSVC10)
On 2013-10-09 2:39 PM, Neil wrote:
Gervase Markham wrote:
* XSLT
Doesn't the XML prettyprinter use XSLT?
It does:
http://mxr.mozilla.org/mozilla-central/source/content/xml/document/resources/XMLPrettyPrint.xsl?force=1
We also use it for about:memory apparently.
Master password. The UI is prone to phishing, it causes all sorts of
problems because of how we use the log in to the NSS database to
implement it, it causes annoying UX for the people that use it, the
cryptography used is useless (bing FireMaster), there's hardly any
resources to do anything
Hey Jet,
I'd say that this greenery project is completely aside from the work
John is doing -- build and tests machines are generally separate.
Are you looking for you (or someone else) to have access to a machine to
green up tests on your own, or looking to have tests run as part of the
normal
On 10/9/13 12:56 PM, David Rajchenbach-Teller wrote:
I am interested, although my buglist is rather full. What kind of help
would be useful?
When it's time, we'll need to:
1. write Loader hooks to make the `import` keyword behave like Cu.import
2. somehow have those hooks installed by
Thanks, everyone, for your thoughtful and voluminous input! I bequeath you the
following behind-the-scenes links so you can see the effect your feedback is
having on DXR's future.
We've collected, de-duped, and categorized your feedback at
https://wiki.mozilla.org/DXR_UI_Refresh#Feedback. If
I think we could have it happen in this order:
1. a way to green up tests on a single machine hooked up to a build server
2. put this on Try
3. put this on production automation
Of course, it would be awesome if we could skip #1 and go to #2 directly as we
green up the tests, as this will open
On 10/09/13 06:29 PM, Jet Villegas wrote:
I think we could have it happen in this order:
1. a way to green up tests on a single machine hooked up to a build server
2. put this on Try
3. put this on production automation
Of course, it would be awesome if we could skip #1 and go to #2
On 10/09/13 06:49 PM, Ben Hearsum wrote:
We could probably make it possible to run them on Try, but I should
defer to Chris AtLee or John Hopkins at this point, as they've got much
more context on this than me.
OK, one more reply from: These _are_ enabled on Try, but the try syntax
to use them
On 10/9/13 6:01 PM, Gervase Markham wrote:
Attack surface reduction works:
http://blog.gerv.net/2013/10/attack-surface-reduction-works/
Removing E4X broke the NSA's EGOTISTICALGOAT attack - a type confusion
vulnerability in E4X.
In the spirit of learning from this, what's next on the chopping
Excellent.
Now to find willing volunteer(s.) Windows 64 represents a key platform for us
now that we've opened up Firefox for high-performance graphics via WebGL and
Canvas. Freeing up the CPU by going to the GPU exposes the next bottleneck:
Memory Bandwidth.
Can you help get the test
On 10/09/2013 12:37 PM, Chris Peterson wrote:
On 10/9/13 9:49 AM, Benjamin Smedberg wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
I'm all for this, although the risk is probably quite small because we
don't expose RDF to content.
Bug 833098 - Kick RDF
Did we start caring about Win64 again recently?
+bsmedberg
- Kyle
On Wed, Oct 9, 2013 at 7:33 PM, Jet Villegas j...@mozilla.com wrote:
Excellent.
Now to find willing volunteer(s.) Windows 64 represents a key platform for
us now that we've opened up Firefox for high-performance graphics
On 10/9/2013 11:18 AM, Boris Zbarsky wrote:
On 10/9/13 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
RDF
Having gone through some of the ancient security bugs, it looks like the
walking-security-hole aspect of RDF was limited
On 2013-10-09 12:01 PM, Gervase Markham wrote:
In the spirit of learning from this, what's next on the chopping block?
In between keep the C++ implementation and scrap entirely is
reimplement in JS, and I think that should be seriously considered for
things like XSLT where there's no
On Wed, Oct 9, 2013 at 4:28 PM, Philipp Kewisch mozi...@kewis.ch wrote:
I think its the wrong conclusion, shouldn't we rather be fixing security
holes and analysing the code for vulnerabilities than removing random things
just because of their potential risk?
Those options are not mutually
On 10/9/13 8:36 PM, Zack Weinberg wrote:
if Web Components lives up to its
promise, perhaps it could be used for the built-in form controls?
For what it's worth, we've tried that with XBL. It died on the
performance and memory usage beach...
-Boris
Hi, Jet:
On 13-10-09 5:35 PM, Jet Villegas wrote:
I'm currently looking for someone to green up the tests on Win64. Can we
dedicate one machine instance (I'm assuming this is on AWS?) for the purpose
of advancing this greenery project? Also, who is the point-person on Release
Engineering
On Wed, Oct 9, 2013 at 2:36 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote:
In the spirit of learning from this, what's next on the chopping block?
JSD. Firebug's the main consumer, AFAIK.
* Most OOM recovery in the JS engine
In the past that has been left alone due to the preference of
On Wed, Oct 09, 2013 at 08:18:16PM -0700, Nicholas Nethercote wrote:
At the summit a few of us were talking about ways to promote Rust.
One idea was to rewrite a smallish, well-separated component of
Firefox in Rust, to (a) gain the benefits (parallelism, safety) of
Rust, and (b) promote Rust
46 matches
Mail list logo
