-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+s8n2yrQH/ipvFxNj4D3cu
Is there any flag I need to setting up?
For example:
app://app-bootstrap/skin/HTMLBrowser.xul
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-pl
On 7/1/15 2:49 AM, Anne van Kesteren wrote:
Platform. There was no strong opposition to the "Intent to deprecate:
Insecure HTTP" thread and in Whistler everyone attending the
deprecating non-secure HTTP session agreed. Do you think this needs to
be approached differently?
Yes. Because taken at
I'll leave some of your points/questions for Richard.
On Wed, Jul 1, 2015 at 10:30 AM, Boris Zbarsky wrote:
> We add lots of features without such Intent threads all the time. Just FYI.
I hope that we can get somewhat better on this. It is rather useful to
have a somewhat large set of people ha
Following up on the message quoted below (Intent to ship on pre-release
channels), we are now planning to ship support for CSS writing-mode,
text-orientation, and related logical-direction properties (things like
block-size and inline-size, margin-block-start, etc) enabled by default
on all cha
So tables and flexbox will be fixed in 41 too?
Congratulations on nearing the end of such a long and difficult project!
Rob
--
oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
osouobojoeocoto otooo ojouodogo
On 1/7/15 11:21, Robert O'Callahan wrote:
So tables and flexbox will be fixed in 41 too?
Both of them are "largely working" in 41 at this point; I believe
they're usable for most common use-cases. For tables, the main
limitation is that is not yet placed correctly; that should
follow in 42
On Wed, Jul 1, 2015 at 6:24 AM, Joshua Cranmer 🐧 wrote:
>
> You'd get the same benefit, I think, by making operator T*() && = delete;,
> syntax which is accepted on gcc 4.8.1+, clang, and MSVC 2015 IIRC.
I once tried this and found it had problematic side effects that made
deploying it difficult
CSS Logical Properties Level 1 doesn't even in WD status yet. Therefore I
assume everything in there can still change fundamentally.
So are you sure logical properties should be shipped already? Could the
writing mode features perhaps be shipped independently from the logical
properties?
This is n
On 1/7/15 13:06, Sebastian Zartner wrote:
CSS Logical Properties Level 1 doesn't even in WD status yet. Therefore
I assume everything in there can still change fundamentally.
So are you sure logical properties should be shipped already? Could the
writing mode features perhaps be shipped independe
On 7/1/15 4:43 AM, Anne van Kesteren wrote:
I hope that we can get somewhat better on this. It is rather useful to
have a somewhat large set of people have insight as to what goes into
Platform.
Sure. I'm just saying that I suspect people underestimate the number of
features we add, the granu
On Wed, Jul 1, 2015 at 8:16 AM, Boris Zbarsky wrote:
> we'd need to decide what
> https://w3c.github.io/webappsec/specs/powerfulfeatures/#is-origin-trustworthy
> step 5 should mean in our particular case
Colloquially: "would you show a lock?"
Unfortunately, conveying the nuance involved in creat
On 7/1/15 12:28 PM, Martin Thomson wrote:
Colloquially: "would you show a lock?"
I just don't see how this can possible match up with what we actually
want here. We don't show a lock for file:// or chrome://, yet the
former is explicitly considered a secure context per spec and the latter
s
[1] Will explain what's probably tripping you up, though I doubt anyone has
tried with app:// URIs before.
[1] https://developer.mozilla.org/en-US/docs/Using_Remote_XUL
On Wed, Jul 1, 2015 at 12:48 AM, 罗勇刚(Yonggang Luo)
wrote:
> Is there any flag I need to setting up?
>
> For example:
>
> app:/
On 6/30/2015 7:35 PM, James Graham wrote:
Web-platform-tests are now running in debug builds on try only. However
due to some teething problems, they are not currently all green. This is
expected to be fixed in the next 24 hours but, in the meantime, if you
see some orange that seems unrelated to
On Tuesday 2015-06-30 17:00 -0400, Richard Barnes wrote:
> Second, when we implement new web platform features, they will be enabled
> only on secure contexts. Exceptions can be granted, but will need to be
> justified as part of the Intent to Implement [3] and Intent to Ship process.
I think thi
This is probably due to
https://dxr.mozilla.org/comm-central/source/mailnews/test/resources/logHelper.js
that registers itself as a console listener and its low-tech feedback
loop prevention. (NB: The quippy file-level comment should be
s/aweswome/Andrew/ for the third instance of awesome.) See
h
The Web API documentation community meeting, with representatives from
the technical evangelism and the API development teams, will take place
on Thursday at 8 AM Pacific Time (see http://bit.ly/1GghwBR for your
time zone).
Typical meetings include news about recent API development progress and
fu
On Wed, Jul 1, 2015 at 7:39 AM, Aryeh Gregor wrote:
> On Wed, Jul 1, 2015 at 6:24 AM, Joshua Cranmer 🐧
> wrote:
> > You'd get the same benefit, I think, by making operator T*() && =
> delete;, syntax which is accepted on gcc 4.8.1+, clang, and MSVC 2015 IIRC.
>
> I once tried this and found it h
On Wed, Jul 1, 2015 at 11:35 AM, L. David Baron wrote:
> On Tuesday 2015-06-30 17:00 -0400, Richard Barnes wrote:
> > Second, when we implement new web platform features, they will be enabled
> > only on secure contexts. Exceptions can be granted, but will need to be
> > justified as part of the
Great discussion and feedback in this thread - plenty to act on.
Thanks Ted Clancy for kicking this off with an impassioned reality
check. And Thanks in particular to Benjamin Francis for summarizing
product requirements and use-cases, and especially to both Ted and Ben
taking the time last week i
On Wed, Jul 1, 2015 at 7:37 PM, Tantek Çelik wrote:
>
> There *is* a pretty strong engineering consensus, in both this thread,
> and other threads *against* any use of JSON-LD, or anything Linked
> Data or otherwise rebranded RDF / Semantic Web, and for good reason.
Indeed, just a few days ago bs
On 2015/07/01 15:53, Robert Strong wrote:
I've only seen those when anything tries to print to the console after a
test has called do_test_finish and in that case I suspect it is due to
xpcshell shutting down, etc.
Robert
Thank you for your observation.
I will investigate if this happens towa
On 2015/07/02 4:30, Andrew Sutherland wrote:
This is probably due to
https://dxr.mozilla.org/comm-central/source/mailnews/test/resources/logHelper.js
that registers itself as a console listener and its low-tech feedback
loop prevention. (NB: The quippy file-level comment should be
s/aweswome/And
I'd definitely like to keep the implementation of whatever formats we
use in Gaia given that this is still an experimental feature and the
use cases are likely to evolve as we get user feedback.
It seems to me that given that our use case here, beyond OG, is only
our "internal" content, I.e. Gaia.
25 matches
Mail list logo