web-extension

Remote Functions Refactor

Overview

Remote functions exist to enable background->tab, and tab->background function delegation (i.e. Call a function in a tab, but have it run in the background and vice versa).

Refactoring has been started to make these functions interfaced and type safe.

Tasks

Grepping the codebase for remoteFunction( shows where it's still being us

Description:

Provide option to keep some segment and provide a submit button below each segment as I don't want to upload the first segment. As I want the first segment but not sure about the consensus and correctness about the first segment.

describe the bug描述问题

describe the problem you encountered 请在此详细描述你遇到的问题，例如问题的表现形式，对你造成了那些影响等

The bing.com search page settings: Country/Region
changes to: China
automatically the first time the translation source is changed to:
Tencent Translate

from the top left button in the EdgeTranslate right panel.
The top left button showed the default source: Google

Any searches from t

Is your feature request related to a problem? Please describe.
We have many Japanese and Chinese speaking users but the interface is only in English

Describe the solution you'd like
Develop an i18n that detects the user language and adapting all the labels accordingly

Describe alternatives you've considered
Let the user select the interface language

Additional context

When a user would like to use yarn, it needs to be installed, even when --skip-install option is used.
I think this check could be moved to the actual install phase, simply throwing a warning like "Yarn is not installed, skipping install. Please install yarn on your machine." is enough.
What do you think, @HaNdTriX ?

The screenshots still follow the old Photon (tab) design, which of course does not

The new design with floating tabs looks very much different. So all images and screencasts need to be re-made.

If anyone wants to contribute, this is a very easy task! You see all files in the [assets/screencasts]

Fonts are stored inside src/fonts/googlefonts and we treat them as static assets. To make it available to our HTML pages we use a webpack plugin that gets a list of all the static assets which is provided by config/webpack/static-files.js. The font files are hardcoded but instead, this needs to be dynamically added to the static files list by reading all the font files inside src/fonts.

any ideas?😄

Hello, my English is poor, so this text was translated using google translate. Please forgive me. I am a user of this plugin, thank you very much for your team for making this plugin. I have a few suggestions I hope your team can consider. I don’t know about web-related programming, and I almost only use C++, so if my suggestion is difficult to implement, then your team can ignore him. Of course,

At the very least, tests for the core parsing code would be great. As new languages are added for localization it would be very helpful to ensure the new patterns are all in alignment.

UI testing is likely not feasible with the extension architecture (someone prove me wrong and I'll be happy).