Re: Fido U2F, two-factor authentication support

[Michael Schwartz (m...@gluu.org)]

Hi guys... if you need a FIDO U2F server to test against, the Gluu Server has 
endpoints built in. Its really easy to deploy on Ubuntu / Centos: 
http://www.gluu.org/docs/admin-guide/deployment/

Also, I recorded a geeky video on how to test FIDO U2F: http://gluu.co/fido-u2f

Basically, check enable, change the default authn mechanism... and you're done. 
Its really easy.

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

[Firefox Desktop] Issues found: November 2nd to November 6th

[Andrei Vaida]

Hi everyone,

Here's the list of new issues found and filed by the Desktop Manual QA 
team last week (Week 45: November 02 - November 06).


Additional details on the team's priorities last week, as well as the 
plans for the current week are available at:


   https://public.etherpad-mozilla.org/p/DesktopManualQAWeeklyStatus



*RELEASE CHANNEL*
none

*BETA CHANNEL*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL  1221489 
Back button is enabled on FirstRun page
NEW 
YES NOBODY


*AURORA CHANNEL*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL 	1220651  
The 'Record allocation stacks' option is disabled if enabling and 
disabling the 'Invert tree' option

NEW 
TBD NOBODY
NORMAL 	1221478  
Conversation titlebar changed color after detaching and reattaching

NEW 
NO  NOBODY
NORMAL  1221486 
	Glitches when clicking mute audio/video icons from conversation window 
and standalone

NEW 
TBD NOBODY
NORMAL  1221507 
	Dotted rectangle on start conversation or close conversation button 
when opening Hello panel

NEW 
YES NOBODY
NORMAL  1221521 
	The snapshots tab is not automatically scrolled to display the last 
taken snapshot

NEW 
TBD NOBODY
NORMAL  1222392 
Aurora is not updated to the latest build on Windows platforms
NEW 
TBD NOBODY


*NIGHTLY CHANNEL
/Nightly 44.0a1/
*
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL  1221074 
	Wrong behavior of the scrubber when an animation is paused and another 
animation is Played and then Stopped

NEW 
TBD NOBODY
NORMAL  1221088 
	The animation displayed in the timeline is not automatically changed if 
the animation-iteration-count is modified

NEW 
TBD NOBODY


/*Nightly 45.0a1*/
SeverityID  Summary Status  Resolution  Is a regression 
Assigned to
NORMAL 	1221084  
"Go Back" button from aboutCertError.xhtml freezes 	ASSI 	

YES Panos Astithas 
NORMAL 	1221512  
The Developer tools are not displayed if restarting twice the Firefox 
browser after changing the value of a boolean pref

NEW 
YES NOBODY
NORMAL  1221980 
	New empty conversation window generated when 'Copy Link'/'E-mail Link' 
buttons are dragged

NEW 
YES NOBODY
NORMAL  1222018 
	[Dell XPS 12 device] Self view is displayed in the right corner of the 
conversation window

NEW 
YES NOBODY


*ESR CHANNEL*
none


Regards,
Andrei Vaida.
Andrei Vaida| QC Team Lead

SOFTVISION | 57 Republicii Street, 400489 Cluj-Napoca, Romania
Email: andrei.va...@softvision.ro  | 
Web: www.softvision.ro 


The content of this communication is classified as SOFTVISION 
Confidential and Proprietary Information.



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

Re: Now measuring Firefox size per-commit. What else should we be tracking?

[Chris AtLee]

On Mon, Nov 9, 2015 at 6:39 PM, William Lachance 
wrote:

> On 2015-11-06 5:56 PM, Mark Finkle wrote:
>
>> I also think measuring build times, and other build related stats, would
>> be
>> useful. I'd like to see Mozilla capturing those stats for developer builds
>> though. I'm less interested in build times for the automation. That data
>> is
>> already looked at by the automation team.
>>
>
> Chris Manchester has volunteered to look into submitting build times in
> automation to perfherder here:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1222549
>
> I actually do think that perfherder has some advantages over the existing
> grafana system, in that it has the capability of being sheriffed easily
> down to the per-commit level by anyone (not just releng/ateam).
>
> We'll see I guess! The proof will be in bugs filed and fixed when
> regressions occur. I really think developer build times are strongly
> correlated with build times in automation, so my hope is that there will be
> a trickle-down effect if this system proves useful.
>

Yes, I agree this is a better approach. Having the build system produce
logs or artifacts than can be ingested by perfherder is a more flexible
model than the one we're currently using.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Now measuring Firefox size per-commit. What else should we be tracking?

[William Lachance]

On 2015-11-06 5:56 PM, Mark Finkle wrote:

I also think measuring build times, and other build related stats, would be
useful. I'd like to see Mozilla capturing those stats for developer builds
though. I'm less interested in build times for the automation. That data is
already looked at by the automation team.


Chris Manchester has volunteered to look into submitting build times in 
automation to perfherder here:


https://bugzilla.mozilla.org/show_bug.cgi?id=1222549

I actually do think that perfherder has some advantages over the 
existing grafana system, in that it has the capability of being 
sheriffed easily down to the per-commit level by anyone (not just 
releng/ateam).


We'll see I guess! The proof will be in bugs filed and fixed when 
regressions occur. I really think developer build times are strongly 
correlated with build times in automation, so my hope is that there will 
be a trickle-down effect if this system proves useful.



Build stats for developers is a black hole though. We don't have a good
idea of the amount of time it takes developers, and this is likely
something that could end up driving productivity down and keep new
contributors from getting involved.


I've heard the same from developers in the Toronto office. I'm honestly 
not sure how helpful tracking developer build times via some 
telemetry-like system would be: everyone knows that things have gotten 
worse over the last year or so, the question is how do we address that?


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

Intent to implement: CSS Mask Image properties

[顧思捷]

*Summary*:
Intend to implement CSS mask. By using this it, you can apply a mask to a
graphical object, so that the graphical object will be painted onto the
background through a mask, thus completely or partially masking out parts
of the graphical object.

*Bug*:
https://bugzilla.mozilla.org/show_bug.cgi?id=686281

*Link to standard*:
https://drafts.fxtf.org/css-masking-1/

*Platform coverage*:
everywhere

Estimated or target release:
Firefox 43

*DevTools bug*:
none

Supported by both Chrome and Safari.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to implement: CSS Mask Image properties

[Jet Villegas]

> *Platform coverage*:
> everywhere
>
>
I'm so happy to see more Core Layout Engine features coming out of the
Taipei office. Nice work, CJ!

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