web-ext-experiments / about Goto Github PK

• Where is your experiment located?

https://github.com/Happy-Ferret/ext-battery

• Can you provide a brief summary of what it does?

Provides functions to query a device's battery status (current battery charge level, charging status -- whether the device is plugged in or running on battery -- time left, time to fully charge).

• Are there any bugzilla bugs it addresses?

Not that I can see.

• Would you like to move the code over to this repository?

Yes.

On that note: I usually release my code under BSD3. Is it possible to do that or will I need to re-license as MPL2?

• Some implementation details worth discussing

Currently, the returned values for all functions are rather verbatim. As opposed to the old BatteryManager API, I made the decision to return values that are already fairly informational but might make it harder to process further.

i e where BatteryManager's charging property would return either true or false, browser.battery.getStatus() currently returns Plugged-in/charging or Running on battery.

I realize now that's not exactly ideal for, say, l10n, so I'm open for suggestions on that front (I could either return true or false here or, perhaps, Adapter/Battery.

TODO: I still plan on implementing Events.

What is a valid schema.json for api schemas? npm run valid-schema would be lovely!

Is this project still supported? I can not install the experimental API in the latest Firefox Nightly.

Curious.

What if my experiment extends an existing API (browser.cookies, in my case)?
Will I be able to provide this as an API experiment to you or will I need to go through different channels?

Note: This is mostly a policy question. From a technological viewpoint, it seems to work just fine (I wrote the experiment earlier today, on behest of a coworker, but just want to make sure I get together all the proper documentation before I even attempt to have it uplifted).

The page at https://webextensions-experiments.readthedocs.io/en/latest/policy.html#policy says:

Currently Experiments can only be run on Firefox Nightly and Firefox Developer Edition.

Per #14 (comment) this is no longer true, only Nightly can be used.

It'd be also worth checking if other parts of the site don't repeat the same incorrect information.

Since Firefox Developers Edition 54.0b14 (32bit / Win7) this extension can't be loaded anymore temporary by using "about:debugging". This seems to be a general issue, extension type 256 isn't recognized as a valid type.

This experiment propose new Javascript API called printservice. Web extensions can use this API to provide functionality related to print process enhancements.

The printservice experiment is located on github https://github.com/edabg/web-ext-experiment-printservice/tree/master.

This experimental API provide functionality to customize print process with features like:
- headers/footers
- media format
- margins
- silent printing (without print dialog)
- range printing
- output format
- print to file
- print to different printers

In general all features supplied by nsIPrintSetting interface.

There is bugzilla issue which address this need also.

If this experiment is useful and can be uplifted and implemented in firefox will be good, because it is needed to successful port of XPCOM jsPrintSetup extension and prolong his life.

Regards,

Dimitar Angelov

https://github.com/kainsavage/moresessions

moresessions is a Web Extension Experiment that provides API support for forgetClosedTab and forgetClosedWindow from the XPCOM nsISessionStore.

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

I do not mind moving the code to this repository (and I can open a pull request if needed)

Ideally, these would be merged into the browser.sessions API and moresessions would go away.

I suggest 'prefs', based on one of the many in Services. I have ideas about the api. Mostly, it's a very simple / contained / useful thing api.

Your required text does not appear to be correct

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC003)

I didn't make this experiment, but seems like it didn't get attention unfortunately.

• Where is your experiment located?
  https://github.com/Smile4ever/webext-experiment-searchengines

• Can you provide a brief summary of what it does?
  Allows querying all search engines, and the default one.

• Are there any bugzilla bugs it addresses?
  https://bugzilla.mozilla.org/show_bug.cgi?id=1268401

• Would you like to move the code over to this repository?
  I'm not behind the experiment. @Smile4ever ?

1. Can you / should you have a 'multi-permission' api? If so, how is that written?

   Example: prefs.read, prefs.set, extension.prefs.read/write

• Context:

I wrote a small addon to help the Firefox product-integrity team validate the Remote Settings feature. It basically exposes some Gecko internal stuff to the addon.

• Where is your experiment located?
  Code is here: https://github.com/leplatrem/remotesettings-pi/tree/v1.0.0/extension

• Can you provide a brief summary of what it does?

It exposes the RemoteSettings.get() and RemoteSettings.onSync() API available in Gecko
https://firefox-source-docs.mozilla.org/services/common/services/RemoteSettings.html

• What's your issue?

It works like a charm on Nightly when I load it via about:debugging.

On Beta, the experiments.remotesettings is undefined.

Note: the addon is not signed.

I would like to know why (I think @rpl told me already but I forgot). Maybe an entry in the FAQ would be helpful.

Thanks!!

• Where is your experiment located?
  https://github.com/tumpio/toolbarpositionchanger/tree/experiment/src/experiment

• Can you provide a brief summary of what it does?
  It let's extensions to move toolbars to any position by index (or to the bottom of browser window) and control the visibility of all toolbars.
  API schema is described in: https://github.com/tumpio/toolbarpositionchanger/tree/experiment/src/experiment#api-schema

• Are there any bugzilla bugs it addresses?
  https://bugzilla.mozilla.org/show_bug.cgi?id=1215064
  https://bugzilla.mozilla.org/show_bug.cgi?id=1332447

• Would you like to move the code over to this repository?
  Sure.