Re: [ANN] Changing the default bug view for BMO

[dlawrence]

Due to some fixes that are taking longer than expected so we are going to push 
the cutover date to January 30th, 2016. Sorry for the delay.

Follow along at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1150541

Thanks
BMO Team


On Friday, January 6, 2017 at 12:10:11 PM UTC-5, Dave Lawrence wrote:
> Announcement: Changing the default bug view for BMO
> 
>As some of you may already know, and maybe even have been using it for a
> while, the BMO [1] team has been working on a new bug view page ((a.k.a
> show_bug.cgi) for some time [2] . The older, stock bug form was not well
> laid out and was difficult to understand, with all of the fields visible
> regardless of how often they were used. The stock form was originally
> designed to  display all of a bug’s data , and users had to adapt their
> workflows accordingly.. The BMO team designed a  completely new and more
> efficient view for the workflows of the majority of BMO users.
> 
>The new bug-editing form has been added to BMO alongside the stock form
> and can be enabled by toggling a user preference [3]. We have been
> incrementally improving it and collecting feedback by those brave enough to
> use it early on. The new form is using more modern design practices and
> therefore is easier for us to improve and expand on. Any new enhancements
> will be done only on the new form going forward. It was code named ‘Bug
> Modal’ due to the modular layout of the page. Each submodule can be
> collapsed out of view and expanded when needed.
> 
>At this time we feel that the form is feature complete and ready to
> become the new default bug form for BMO. We have been tracking the final
> blockers in a bug report [4], and the last blockers are being wrapped up
> this week. We wanted to let everyone know of the coming changeover in
> advance so that we can get last-minute feedback. The older, stock bug view
> form will still be around, and we will update the user preference to let
> users switch back to the old one[3]. In the future, we will be removing the
> old form altogether after fixing a few more bugs[6], and we will make
> another announcement beforehand. Removing the old code will make it easier
> on us from a maintenance standpoint.
> 
> 
> 
>Barring any issues with landing the last blockers, we are hoping to do
> the changeover on January 16th, 2017. Until then, if this is the first time
> you have heard of this new feature,  go ahead and give it a try. Any bugs,
> comments, or ideas for improvement of the modal form can be reported in BMO
> [5].
> 
> Thanks!
> 
> BMO Team
> 
> 
> [1] https://bugzilla.mozilla.org
> 
> [2] https://globau.wordpress.com/2015/03/31/bmo-new-look/
> 
> [3]
> https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_experiments_row
> 
> [4] https://bugzilla.mozilla.org/show_bug.cgi?id=1150541
> 
> [5]
> https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org=User%20Interface:%20Modal
> 
> [6] https://bugzilla.mozilla.org/show_bug.cgi?id=1273046

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

Intent to Implement: Module scripts (ES6 modules)

[jcoppeard]

Summary:

An HTML 

Re: Is it possible to implement "click to play" for Adobe Flash in XULRunner app?

[Benjamin Smedberg]

You have to manage the UI yourself. Firefox does this with a combination of
applying an overlay to the disabled Flash which shows the grey UI, plus
script that sets permissions and activates plugins appropriately. Because
of e10s, that code is split between multiple files, but you should try to
read and understand the following bits:

http://searchfox.org/mozilla-central/source/browser/modules/PluginContent.jsm
- frame script (runs in content process)
http://searchfox.org/mozilla-central/source/browser/base/content/browser-plugins.js
- UI script (runs in chrome process)
Binding files that set up the click-to-play overlay UI:
http://searchfox.org/mozilla-central/source/toolkit/pluginproblem/content

Be aware that we're actively removing plugin support from the Mozilla
platform; soon only Flash is likely to work, and after a while NPAPI might
be removed completely. So don't get too wedded to plugin support in
XULRunner as a long-term strategy.

--BDS


On Wed, Jan 11, 2017 at 10:01 PM, 段垚  wrote:

> Hi,
>
> In Firefox, "click to play" can be enabled by setting pref
> "plugin.state.flash" to 1.
>
> However, when I do this in a XULRunner app, flash plugin is disabled
> completely.
>
> Is this feature unavailable to XULRunner? If so, how can I implement it?
>
>
> Thanks.
>
>
> Duan Yao.
>
>
> ___
> 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

INQUIRY

[KASARLA SHIRISHA]

What are the projects based on AngularJs in GSOC16
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform