gt; Again, it's bug 1322769 if you want to comment or follow along.
>
As I said before, this approach is, IMO, much too complicated; splitting
the reusable parts of Servo into their own repositories, as we have done
before, would be a much simpler solution.
However, as it seems the decisi
art of the implementation:
<https://hg.mozilla.org/integration/mozilla-inbound/rev/ddfcb1823adc>
Security & Privacy Concerns: none
(Please direct any further questions to Mats, who implemented the API.)
HTH
Ms2ger
___
dev-platform mailing list
dev-platfo
band this WG and
move any remaining useful work to the WHATWG.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t.
>
> In order to be compliant the spec, it's time to get rid of this.
> Any objection?
>
... and we will stop dispatching the clone event.
This is https://bugzilla.mozilla.org/show_bug.cgi?id=790919
Really great to finally see it gone!
Ms2ger
_
ll be shared with other vendors (and
Servo)?
Thanks
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
nsition from MXR to its more modern equivalent, DXR (
> https://dxr.mozilla.org), instead of bringing MXR back online.
I wish the years of complaining about MXR had led to an equally useful
replacement for it by now.
Sad to see it go.
Ms2ger
___
dev-p
nd only creates a reflector when JS code needs it.
> the memory management arrangements of the two
> engines are fundamentally different and, therefore, the same WebIDL
> bindings won't work.
... but your conclusion remains correct.
HTH
Ms2ger
.
How about Edge?
Should we implement an unprefixed version as well?
> Preference behind which this will be implemented:
> layout.css.prefixes.webkit
Should this have a more specific pref?
Thanks
Ms2ger
___
dev-platform mailing list
dev-platform@
nd paste from the
> rust-encoding UTF-8 and UTF-16 converters.
I agree that it is useful to have code looking like the spec in the
general case. However, if we were to get to the point where that was
the only argument against unifying your proposed library and
rust-unicode, I think we should
and maybe Aurora for now.
> I don't remember what the current conventional wisdom about
> prefixing is, but I would be open to shipping with a prefix if
> people thought that would ease pain in the eventual transition.
No. Nonononononononono.
Ms2ger
-
om/feature/5743723954569216
>
Do we have tests in web-platform-tests that show our implementation is
interoperable with Blink?
I believe there was a capitalization issue with this feature; has it
been solved and the solution implemented everywhere?
Thanks
Ms2ger
-BEGIN PGP SIGNATURE-
i
geSmoothingEnabled
>
>
>
> Blink and WebKit unprefixed awhile ago, too:
> https://code.google.com/p/chromium/issues/detail?id=277199
> https://bugs.webkit.org/show_bug.cgi?id=147803
Do we have a test suite that shows our implementation is interoperable
with
to have the final word on this)
Strongly in favour for all the reasons you mentioned.
Thanks
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJWKftoAAoJEOXgvIL+s8n2ALEH/3quXXrs7lAn1qiWjdj0nfTE
r6qbmHHUL1OlfkipeFLy+vjLmI2g5ep/aKlAfYBILowaQgzFlXUiTBiz1+Yz2ChD
1UzCHOGKxcPLNYVpgEu5snBjdWhPk1DJZk
form to bring up fundamental issues
> for the first time at this stage.)
>
> (Sorry, should have sent these out a bit sooner.)
Does this mean that the W3C is claiming that the features in these
forks have interoperable implementations, and should we point out what
utter no
W3C WICG, but given the state of the
> world, us shipping this with or without a spec can hardly cause any
> more harm.
Please submit tests to web-platform-tests and create a pull request to
the HTML standard.
Thanks
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJWJN+pA
not seem to support the claim that they intend to ship
this feature. No intent-to-ship is mentioned, and it appears the
intent-to-implement has not been sent.
Have other browser vendors provided any implementation feedback?
Thanks
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJV+9MXAAoJEOXg
s a terrible idea. (Even if we're
the only Member raising a formal objection, I suspect Mike(TM) Smith
would be happy to amplify the message internally.)
OTOH, maybe we should just move the remaining useful specs in WebApps
to WHATWG; that'd solve the issue once and for all.
HTH
Ms2ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/2015 03:36 PM, Ehsan Akhgari wrote:
> Hmm, I see. Have you considered the implications of making the
> alias falsey in conditions, similar to document.all?
No. No. Nononononono.
Ms2ger
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/10/2015 11:25 PM, Vladan Djeric wrote:
> Intern presentation schedule:
> https://mana.mozilla.org/wiki/display/globalstaffing/2015+Intern+Prese
ntations
Nothing
>
public?
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVyaLMAA
to
kick them out, they want to return through this back door. If the
handful of people who still care about it want to continue wasting
each other's time, they can always start a Community Group, or move to
another standards development organization.
HTH
Ms2ger
-BEGIN PGP SIGNATUR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/01/2015 01:35 AM, James Graham wrote:
> Web-platform-tests are now running in debug builds on try only.
>
\o/
Thanks for getting this up and running!
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVk5APAAoJEOXgvIL+s8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/22/2015 05:51 AM, J. Ryan Stinnett wrote:
> On Sched, it appears the Servo session is scheduled for Friday, 1 -
> 3 PM, is that now the correct date and time?
That's correct.
HTH
Ms2ger
-BEGIN PG
Please file a bug on the spec to add it (even though this is the
webperf wg), and keep it out of release builds at least until it's
been discussed there.
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVXf7hAAoJEOXgvIL+s8n2ON4H/joOtkdA6pAqsEJmFZebZmZH
CND5saMByYUx78y9eH81PWFVzthD
this include `mochitest-1` and friends? These are a lot easier to
use than having to figure out the exact incantation for the chunked
suites.
HTH
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVU7vsAAoJEOXgvIL+s8n229EH/A+dFtY8nqDOCywDGBjgU8cL
V32tfYfv3tISII8YCP9Jsl58SW3YFpUk+inneUdVKXYce5OAkr4f
ll handle
>> the landing when inbound is open and green.
>
>
> Isn't the point of inbound supposed to be that it's safe to land
> even without 100% confidence? Here's the guidance from the Wiki:
"without 100%" doesn't mean "with
or is().
Thanks to everyone who helped bring this home!
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVLhlwAAoJEOXgvIL+s8n27TEH/RTBfCQmN0dwDzzRGPsYT9ya
ztmFfpJq2NKe85YX9XnO+yLha9Lvc2V83J4SHRC0PpJgKEfgR3DAswCDnX+MOD3e
7PfXqkY6ceVhrrPz1b0TxWWCnVvW9OyjlxhAjH7k8K96T0uBvcrB3q0AKFL
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#h-event-modifier-initializers
>
>
>
What are other browsers planning to do? Do we have any tests in wpt
that could show interop?
- --
Thanks
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJVJi0jAAoJEOXgvIL+s8n24DEH
t have been suggested, yes. (I've heard
suggestions for async innerHTML too, but I don't think that was in the
context of Servo.)
Either way, while some people have been dreaming about such APIs,
we're not actually working on any, or planning to start working on them.
HTH
M
he testing story? Do we pass the web-platform tests
(<https://github.com/w3c/web-platform-tests/tree/master/subresource-integrity>)?
Do we run them in automation? Do we intend to extend
the tests to a level where we can be confident about interoperability
with other browsers?
Thanks
Ms
ef and Release
>> impossible, and not raw pointers in general.
>
> Well, I did pick that project up but for some reason it was never
> finished (don't remember what.) But that's not what I was talking
> about. See bug 1114683 for an example of what I was talk
tch files to use the new paths, see:
>> https://gist.github.com/poiru/b266b75473a8d9f71d33
>
> Did we not coordinate this with the sheriffs at all? This needs to
> be merged to all trees as soon as possible to keep the merge pain
> down.
Philor merged to m-c and fx-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2014 02:09 AM, Kyle Huey wrote:
> The simplest way to break the installer down is by the files in
> it.
>
> e.g. http://khuey.pastebin.mozilla.org/6781501
For future reference:
> mozilla@KHUEY-19294 /c/dev/scratch $ wget
> ftp://ftp.mozilla
o avoid.
>
> Perhaps http://gitmirror.mozilla.org/ should be our project
> directory.
Looks like the instructions to add repos are on intranet; why?
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJULCydAAoJEOXgvIL+s8n2+0MIAJKuWFkVTXpNwdirhBY+P/Zj
4yE8U3SAwzYoG+rTWpqozUeGQDhtDKlxM9
st and lead to
you being pressured to retract them at worst, I believe the answers
that make the most sense are
* Regarding the HTML5 specification, my organization: abstains from
this review.
* My organization: does not expect to produce or use products or
content addressed by this specification
H
finitely shouldn't introduce new init*Event methods.
Ms2ger
-BEGIN PGP SIGNATURE-
iQEcBAEBAgAGBQJUEVzEAAoJEOXgvIL+s8n2YWYH/i9h3e3GvQ9dPrYYg72F/mdD
BXdyHiyKarz4dSI8H0UJHwDhCtBKi92AskHhCeT3l4KX4h7pX87144LYNYiZ9qzv
rMXDFvf5Oo8M4uaEPo82z1M2OW6jADuFCfs4SeK+1aqW5DLRRM
name "external" so it's easily
> identified as needing external access.
I don't think anyone is in agreement with this, actually. The
suggestion was to use a manifest annotation *instead of* the
unnecessary directory structure.
HTH
Ms2ger
-BEGIN PGP S
to
> maintain backwards capability.
>
> So I guess I'd like to determine if the approach I've outlined is
> reasonable, and I'd like to get an opinion on whether we should
> use deviceStorage or mozDeviceStorage.
The policy [2] is crystal-clear: we don't add moz
sensible approach to
achieve that goal would be to adopt the testharness.js methods, which
are also more consistently named, have better behaviour for the
shorter-name methods, and are documented more clearly.
HTH
Ms2ger
___
dev-platform mailing list
s(num) == Infinity) {
throw new Error("This need to be a non-negative whole number");
}
Well, it adds up. :) Even now I can replace the fifth condition with
!Number.isFinite(num).
>
One could use "if ((num | 0) !== num) { ... }". That should be
equivalent f
Hi Chris,
The spec might: <http://www.whatwg.org/html/#dom-navigator-mimetypes>.
HTH
Ms2ger
On 05/12/2014 12:18 PM, Chris Mills wrote:
Hi all
Dann (see below) had a query about the MimeType objects returned by
NavigatorPlugins.mimeTypes. Does anyone here have any advice about dealin
On 04/15/2014 11:08 PM, Joshua Dover wrote:
as this current specification is not on a standards track
(and will probably not be compatible with what we have now).
That sounds like a clear "no" to me.
HTH
Ms2ger
___
dev-platform mailin
On 03/12/2014 08:40 AM, Rik Cabanier wrote:
*Link to standard:*
http://wiki.whatwg.org/wiki/CanvasOpaque
That's not a standard...
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
, forgot to mention, sorry. Hoped it's obvious from looking into the
IDL file.
Why do you take this as "two differences"?
netwerk vs network
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.o
, as
they're in the global namespace, we still tend to prefix, so I guess nsIFoo.
(Not cross-posting to ask.m.o until it supports persona.)
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinf
s, so people who are not
peers should not be listed as preferred reviewers.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t JS
hackers" is necessarily accurate.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ne else than
Benjamin, and only in his modules the NS_ENSURE_* macros have been
effectively deprecated.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e imported from WebKit
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
d suggest:
| nsIScriptSecurityManager* ssm = nsContentUtils::GetSecurityManager();
| rv = ssm->GetSimpleCodebasePrincipal(originURI,
|
getter_AddRefs(providedPrincipal);
| if (NS_WARN_IF(NS_FAILED(rv))) {
HTH
Ms2ger
___
dev-platform mailing list
bug should be fixed?
As was mentioned before, very much the former.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
engine for some of our CVS repositories, of which I
think none are in active development.
It's the source of truth for pre-mercurial Gecko history; I find myself
having to use it surprisingly often.
HTH
Ms2ger
___
dev-platform maili
s explain how to
find the doc.
The etherpad was at <https://etherpad.mozilla.org/commonissues>. Since
it's been out of the topic since last March, though, I don't think
anything there is particularly common still.
HTH
Ms2ger
automation. On one
hand, this could cause more bustage when changes that built locally turn
out not to have enough includes; on the other, it might be better than
having to fix up a dozen unrelated files whenever you add a new one.
Thoughts?
Ms2ger
___
clue where to start
http://logbot.glob.com.au/?c=mozilla%23content&s=30+Sep+2013&e=30+Sep+2013#c137495
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 08/20/2013 02:15 AM, Nicholas Nethercote wrote:
They can be replaced by forward declarations of a handful of types,
e.g.:
struct jsid;
This is not actually the case: jsid is a typedef for ptrdiff_t in
release builds, so you'll still need to include jspubtd.h for it.
HTH
M
ow if that has changed since.)
* Would you want to additionally consider using something like JS-Lint
for our codebase?
I don't want to derail this thread, but AIUI, JSLint enforces Douglas
Crockford's style, which is not necessarily something anyone else wants
to use
).spec does not always return "str".
Actually, the issue is that makeURI(makeURI(str).spec).spec !=
makeURI(str).spec.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
test jobs from starting.
Test jobs are kicked off before 'make check' starts.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 04/21/2013 08:15 PM, David Ascher wrote:
Mine is crashing on startup. Can't even get to profile chooser dialog.
That'll be bug 863646.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/li
client.mk. (Please correct me if I am wrong.)
This should say …about wanting it *on buildbot*. I have not heard
sheriffs being very vocal about anything to do with local builds. (Which
means that that particular request could have been solved with an opt-in
rather than an opt-out flag.)
items and know where to add items.
Fully agree, with the exception that I'm not sure this is a safe
transformation for *DIRS.
--
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
/editing) such that my
patches experienced bitrot. Please comment here or in bug 852065 as I would
like to land these patch this by this weekend.
I do not understand the purpose of these change. They do not appear to
have any benefits.
Ms2ger
___
dev
at benefit it would bring to put them further away.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
zilla-Inbound.
(And, worse, that might actually be wasting the time of many others
by increasing wait times on Try.)
To be honest, at this point, it feels like using Try too rarely is a
bigger problem than using it too often.
Ms2ger
___
dev-platform ma
IDL. XPIDL's
consistency here, IMO, saves time when implementing an interface: you
can focus on the actual implementation, rather than the binding code.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t; The reason I ask is that we're supposed to write
xpcshell tests in preference to mochitests when possible, and I'd
hate the preference to change to be in favor of mochitests, because
xpcshell tests are much more convenient (and faster) to write and
run.
Kyle already answered this.
H
test fails intermittently in Gecko doesn't
necessarily imply that it will also fail intermittently in other
browsers; these failures often point to actual Gecko bugs, rather than
test issues.
HTH
Ms2ger
___
dev-platform mailing list
de
On 08/16/2012 06:21 PM, Ehsan Akhgari wrote:
On 12-08-16 11:34 AM, Ms2ger wrote:
On 08/16/2012 05:10 PM, Ehsan Akhgari wrote:
I think this is generally a good idea. I have a few questions before
jumping in to agree though.
1. Is the current testharness.js API the documentation at the
tests as well, some of which are
already running on tinderbox.
HTH
Ms2ger
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ch) on the first of July.
I find your reaction to this situation extremely rude and disrespectful
to people who put their time into keeping our tree green; a hard enough
job without people insisting their unreliable tests *absolutely need* to
be enabled.
Thank
70 matches
Mail list logo