Chrome extension

Description

No words honestly. We reject features and drop content from the header to avoid this stuff and they keep adding buttons. Let's limit the buttons to 50% of the screen and then have them wrap

Screenshot

Example URL

https://gi

We want to add a link to our content guidelines before a user submits a source request. This will provide users a better understanding of what the process is and what content we allow, and what not.

How to get started?

• This

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.

Is your feature request related to a problem? Please describe.
In my opinion, it would be nice to have an option/flag to allow users to turn off line numbers. I am used to launch Altair with in not full-screen mode and have 3 columns: request, result and docs. Line numbers generally is useless and occupy valuable horizontal space.

Describe the solution you'd like
Checkbox "Show line n

Update styling to match new Chrome/devtools flat design.

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