Delayed Bugzilla Emails

2020-08-05 Thread glob
Due to an issue that occurred during the bugzilla.mozilla.org deployment 
yesterday (5th August), emails generated immediately following the 
deployment (2pm to 4pm US/Eastern) have been delayed.


As the systems work through the backlog of approximately 12 thousand 
emails you may receive emails out of sequence.


See https://bugzilla.mozilla.org/1657542 for more information.

--
glob — engineering workflow manager — moz://a

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


Re: Intent to prototype: Payment Handler API

2020-08-05 Thread mcac...@mozilla.com
After some initial prototyping, we've decided to put the Payment Handler API on 
hold for now. We are instead focusing on continuing to improve credit card 
autofill in Firefox.  

We plan to continue working with the W3C's Web payments working group to see if 
we can come up with something better to enable secure payments on the web. 

On Monday, July 13, 2020 at 10:55:23 AM UTC+10, Dan Glastonbury wrote:
> Summary: 
> 
> The Payment Handler API allows web applications to register themselves as 
> capable of "handling payments". That is, they can handle payment requests 
> coming from the Payment Request API. Traditionally, handling payment 
> requests has been limited to OS specific payment handlers, and only to 
> particular browsers (Apple Pay on Safari, Google Pay for Chrome, for 
> instance). This new API has the potential to disrupt the payments 
> ecosystems, while also providing some much needed security to prevent 
> credit card fraud in the payments space. 
> 
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1465682 
> 
> Standard: https://w3c.github.io/payment-handler/ 
> 
> Platform coverage: Desktop initially, Android later. 
> 
> Preference: dom.payments.handler.enabled (plus potentially others at 
> dom.payments.*) 
> 
> DevTools bug: none yet. We're still working out the details of what we 
> might actually want. 
> 
> Other browsers: 
> 
> * Chrome shipped since version 68 
> 
> web-platform-tests: 
> https://github.com/web-platform-tests/wpt/tree/master/payment-handler 
> 
> Secure contexts: Yes 
> 
> Is this feature enabled by default in sandboxed iframes? 
> 
> No. We are thinking that it's only available to top-level browsing 
> contexts, otherwise controlled by permission policy. 
> 
> Link to standards-positions discussion: 
> 
> https://mozilla.github.io/standards-positions/#payment-handler (worth 
> prototyping) 
> 
> How stable is the spec: some parts are stable (e.g., some of the events) … 
> other parts, not so much (e.g., payment instruments database). 
> 
> Security & Privacy Concerns: a bunch of ongoing work is happening in this 
> space together with our colleagues at Google, as well as with the financial 
> industry at large. We hope that to see all that work reflected back in the 
> spec as we do our prototyping and find issues.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


happy bmo push day!

2020-08-05 Thread David Lawrence
the following changes have been pushed to bugzilla.mozilla.org:

(tag: https://github.com/mozilla-bteam/bmo/tree/release-20200805.1)

https://bugzil.la/1643526 : Attachment comments don't render markdown,
but their preview does
https://bugzil.la/1654456 : [needinfo] Provide instructions and
guidance when needinfo is requested of the bug's reporter
https://bugzil.la/1654370 : Remove remaining code that references
Firefox OS from BMO code base
https://bugzil.la/1655808 : Send guided bug flow users to GitHub for
Fenix issues

-- 
David Lawrence 
Mozilla, Inc.

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