Rendering meeting, Monday 2:30pm PDT ("the earlier time")

[Milan Sreckovic]

The Rendering meeting (https://wiki.mozilla.org/Platform/GFX#Biweekly_meetings) 
is about all things Gfx, Image, Layout, and Media. 
It takes place every second Monday, alternating between 2:30pm PDT and 5:30pm 
PDT. 

The next meeting will take place on Monday, May 5 at 2:30 PM US/Pacific 
Please add to the agenda: 
https://wiki.mozilla.org/Platform/GFX/2014-May-5#Agenda 

San Francisco - Monday, 2:30pm 
Winnipeg - Monday, 4:30pm 
Toronto - Monday, 5:30pm 
GMT/UTC - Monday, 21:30 
Paris - Monday, 11:30pm 
Taipei - Tuesday, 5:30am 
Brisbane - Tuesday, 7:30am 
Auckland - Tuesday, 9:30am 

http://arewemeetingyet.com/Toronto/2014-05-05/17:30/Rendering%20Meeting

Video conferencing: 
Vidyo room Graphics (9366) 
https://v.mozilla.com/flex.html?roomdirect.html&key=FILzKzPcA6W2 

Phone conferencing: 
+1 650 903 0800 x92 Conf# 99366 
+1 416 848 3114 x92 Conf# 99366 
+1 800 707 2533 (pin 369) Conf# 99366
--
- Milan

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to implement: WebRTC identity and media isolation

[Martin Thomson]

We’re hoping to be first here.

I’m told that Chrome is implementing it, but I haven’t seen any actual 
evidence.  I’m seeing lots of interest from my old colleagues at Microsoft, but 
[1].

[1] http://status.modern.ie/webrtcwebrtcv10api

On 2014-05-02, at 14:19, Ehsan Akhgari  wrote:

> Thanks, Martin!
> 
> Do you know if other UAs are also implementing this API?
> 
> On 2014-05-02, 4:09 PM, Martin Thomson wrote:
>> Summary:
>>   WebRTC enables peer-to-peer communications.  Identity features enable the 
>> identification of WebRTC peers using a generic identity provider interface.  
>> Stream isolation provides sites a way to foreswear access to media so that - 
>> in combination with identity - users can be sure that their media is being 
>> sent to a specific peer (and that media from that peer came from that peer). 
>>  This enables secure calling that does not rely on trust in the web site or 
>> application that performs signalling.
>> 
>> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=901261
>> Link to standard: http://dev.w3.org/2011/webrtc/editor/webrtc.html#identity
>> Platform coverage: Desktop, Android, Firefox OS
>> Estimated or target release: 32, Firefox OS 2.0
>> Preference behind which this will be implemented: 
>> media.peerconnection.identity.enabled (dom.messageChannel.enabled also needs 
>> to be true)
>> 
>> ___
>> dev-platform mailing list
>> dev-platform@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
>> 
> 

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to implement: WebRTC identity and media isolation

[Ehsan Akhgari]

Thanks, Martin!

Do you know if other UAs are also implementing this API?

On 2014-05-02, 4:09 PM, Martin Thomson wrote:

Summary:
   WebRTC enables peer-to-peer communications.  Identity features enable the 
identification of WebRTC peers using a generic identity provider interface.  
Stream isolation provides sites a way to foreswear access to media so that - in 
combination with identity - users can be sure that their media is being sent to 
a specific peer (and that media from that peer came from that peer).  This 
enables secure calling that does not rely on trust in the web site or 
application that performs signalling.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=901261
Link to standard: http://dev.w3.org/2011/webrtc/editor/webrtc.html#identity
Platform coverage: Desktop, Android, Firefox OS
Estimated or target release: 32, Firefox OS 2.0
Preference behind which this will be implemented: 
media.peerconnection.identity.enabled (dom.messageChannel.enabled also needs to 
be true)

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform



___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to implement: WebRTC identity and media isolation

[Martin Thomson]

Summary:
  WebRTC enables peer-to-peer communications.  Identity features enable the 
identification of WebRTC peers using a generic identity provider interface.  
Stream isolation provides sites a way to foreswear access to media so that - in 
combination with identity - users can be sure that their media is being sent to 
a specific peer (and that media from that peer came from that peer).  This 
enables secure calling that does not rely on trust in the web site or 
application that performs signalling.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=901261
Link to standard: http://dev.w3.org/2011/webrtc/editor/webrtc.html#identity
Platform coverage: Desktop, Android, Firefox OS
Estimated or target release: 32, Firefox OS 2.0
Preference behind which this will be implemented: 
media.peerconnection.identity.enabled (dom.messageChannel.enabled also needs to 
be true)

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: intent to ship: drawFocusIfNeeded

[Ehsan Akhgari]

On Thu, May 1, 2014 at 4:10 PM, Rik Cabanier  wrote:

>
>
>
> On Thu, May 1, 2014 at 11:58 AM, Ehsan Akhgari wrote:
>
>> On 2014-05-01, 2:22 PM, Rik Cabanier wrote:
>>
>>>
>>>
>>>
>>> On Thu, May 1, 2014 at 10:49 AM, Ehsan Akhgari >> > wrote:
>>>
>>> Hi Rik,
>>>
>>> How extensive is our testing of this feature?  I'm very surprised
>>> that bug 1004499 was not caught by a test when you landed this.
>>>
>>>
>>> I wrote a number of mochi tests. In addition Dominc (from Google) wrote
>>> a more real world example [1] and I checked that the blink test files
>>> also work in Firefox.
>>> There are also a number of W3C tests that check that the implementation
>>> follows the spec. [2]
>>>
>>
>> Sounds good!  If you think the existing mochitests don't give us enough
>> coverage, we should try to add more tests.
>>
>>
>>  Can you give me an example where 1004499 would be triggered? I will
>>> update that bug with an extra test.
>>>
>>
>> We only draw the focus ring if something is focused by the keyboard.  In
>> order to simulate that in a mochitest, you can give your DOM element a
>> @tabindex attribute, and then use syntehsizeKey to generate VK_TAB events
>> to focus that DOM element.  In order to test the opposite case, you can use
>> synthesizeMouse to simulate setting the focus using the mouse.
>
>
> Is that always the case?
>

I think so, for content at least.


> In our tests, we can also use elements that can get the focus by default
> (such as  and ) and we can focus them by calling 'focus()' on the
> element.
>

Please check with Neil Deakin, he really knows this stuff the best.  I just
wanted to make sure we have good test coverage here.

Thanks!

--
Ehsan



>
>
>>
>>  1: http://www.w3.org/2013/09/accessible_canvas_clock.html
>>> 2:
>>> https://github.com/w3c/web-platform-tests/tree/master/
>>> 2dcontext/drawing-paths-to-the-canvas
>>>
>>>
>>> On 2014-04-30, 8:44 PM, Rik Cabanier wrote:
>>>
>>> Primary eng emails
>>> caban...@adobe.com 
>>>
>>> *Spec*
>>> http://www.w3.org/html/wg/__drafts/2dcontext/html5_canvas_
>>> __CR/#dom-context-2d-__drawfocusifneeded
>>>
>>> >> CR/#dom-context-2d-drawfocusifneeded>
>>>
>>> *Summary*
>>>
>>> The drawFocusIfNeeded API is a method on the canvas context that
>>> allows a
>>> user to draw a focus ring when a fallback element is focused.
>>> See
>>> http://www.w3c-test.org/__2dcontext/drawing-paths-to-__
>>> the-canvas/drawFocusIfNeeded___001.html
>>>
>>> >> the-canvas/drawFocusIfNeeded_001.html>
>>> for
>>> an example.
>>>
>>> *Blink:*
>>>
>>> This is currently behind a runtime flag but engineers from
>>> Samsung is going
>>> to send an intent to ship to the blink mailing list.
>>> _
>>> dev-platform mailing list
>>> dev-platform@lists.mozilla.org
>>> 
>>> https://lists.mozilla.org/__listinfo/dev-platform
>>> 
>>>
>>>
>>>
>>>
>>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Callback from xpcom c++ in multi thread scenerio

[Neil]

lukaszb wrote:


Basicly idea is easy from javascript we call "db wrapper" with take function (callback) 
as argument (that function implement xpidl interface with scriptable and function annotations), in 
"db wrapper" component we run thread where real database connection exists and fetch 
data, then we join to main thread and return result by callback (mentioned above). BUT application 
crash after calling callback (now there is now proxies api) and I assume that callback i collected 
by collected by javascript GC. (When all happens only in main thread then all it's ok).

Strangely enough I recently fixed a similar-looking problem in 
Thunderbird. There the problem was that the callback was being released 
on the database thread instead of the main thread.


You could of course be extremely careful with your references so that 
your callback never gets released on the database thread. Alternatively, 
these classes make it trivial for you: 
http://mxr.mozilla.org/mozilla-central/source/xpcom/glue/nsProxyRelease.h#67


--
Warning: May contain traces of nuts.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Callback from xpcom c++ in multi thread scenerio

[lukaszb]

I'm developing windows app based on xulrunner, but now I have major problem and 
nowhere can find solution, that is why I'm writing here.
Orginaly app was on xulrunner 11, but now we trying to change core xpcom c++ 
component that connects to database (to be specific we trying add support for 
oracle
database, now it is only mariadb/mysql) - we call it "db wrapper".
To move things forward (and this is oportunity to change xulrunner version to 
newer) we decide to use xulrunner 28.0 and problems occurs. This new
xulrunner version doesn't have proxies objects and I don't have a clue how to 
implement callback from oure component to javascript.
Basicly idea is easy from javascript we call "db wrapper" with take function 
(callback) as argument (that function implement xpidl interface with
scriptable and function annotations), in "db wrapper" component we run thread 
where real database connection exists and fetch data, then we join to
main thread and return result by callback (mentioned above). BUT application 
crash after calling callback (now there is now proxies api) and I assume that 
callback i collected by
collected by javascript GC. (When all happens only in main thread then all it's 
ok).
I can't figure out how to extend lifetime of callback.
LIB: XULRunner 28
OS: Windows 7 - 32bit.

I'm trying using this pattern  
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Guide/Cross-thread_calls_using_runnables
 with that diffrence that I'm using nsCOMPtr to callback interface instade of 
pointer to function.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform