Element

Element (formerly known as Vector and Riot) is a Matrix web client built using the Matrix React SDK.

Supported Environments

Element has several tiers of support for different environments:

• Supported
  • Definition: Issues actively triaged, regressions block the release
  • Last 2 major versions of Chrome, Firefox, and Safari on desktop OSes
  • Latest release of official Element Desktop app on desktop OSes
  • Desktop OSes means macOS, Windows, and Linux versions for desktop devices that are actively supported by the OS vendor and receive security updates
• Experimental
  • Definition: Issues accepted, regressions do not block the release
  • Element as an installed PWA via current stable version of Chrome, Firefox, and Safari
  • Mobile web for current stable version of Chrome, Firefox, and Safari on Android, iOS, and iPadOS
• Not supported
  • Definition: Issues only affecting unsupported environments are closed
  • Everything else

For accessing Element on an Android or iOS device, we currently recommend the native apps element-android and element-ios.

Getting Started

The easiest way to test Element is to just use the hosted copy at https://app.element.io. The

develop

To host your own copy of Element, the quickest bet is to use a pre-built released version of Element:

1. Download the latest version from https://github.com/vector-im/element-web/releases
2. Untar the tarball on your web server
3. Move (or symlink) the

   riot-x.x.x

   directory to an appropriate name
4. Configure the correct caching headers in your webserver (see below)
5. If desired, copy

   config.sample.json

   to

   config.json

   and edit it as desired. See the configuration docs for details.
6. Enter the URL into your browser and log into Element!

Releases are signed using gpg and the OpenPGP standard, and can be checked against the public key located at https://packages.riot.im/riot-release-key.asc.

Note that for the security of your chats will need to serve Element over HTTPS. Major browsers also do not allow you to use VoIP/video chats over HTTP, as WebRTC is only usable over HTTPS. There are some exceptions like when using localhost, which is considered a secure context and thus allowed.

To install Element as a desktop application, see Running as a desktop app below.

Important Security Note

We do not recommend running Element from the same domain name as your Matrix homeserver. The reason is the risk of XSS (cross-site-scripting) vulnerabilities that could occur if someone caused Element to load and render malicious user generated content from a Matrix API which then had trusted access to Element (or other apps) due to sharing the same domain.

We have put some coarse mitigations into place to try to protect against this situation, but it's still not good practice to do it in the first place. See https://github.com/vector-im/element-web/issues/1977 for more details.

Building From Source

Element is a modular webapp built with modern ES6 and uses a Node.js build system. Ensure you have the latest LTS version of Node.js installed.

Using

yarn

npm

1. Install or update

   node.js

   so that your

   node

   is at least v10.x.
2. Install

   yarn

   if not present already.
3. Clone the repo:

   git clone https://github.com/vector-im/element-web.git

   .
4. Switch to the element-web directory:

   cd element-web

   .
5. Install the prerequisites:

   yarn install

   .
   • If you're using the

     develop

     branch, then it is recommended to set up a proper development environment (see Setting up a dev environment below). Alternatively, you can use https://develop.element.io - the continuous integration release of the develop branch.
6. Configure the app by copying

   config.sample.json

   to

   config.json

   and modifying it. See the configuration docs for details.

7. yarn dist

   to build a tarball to deploy. Untaring this file will give a version-specific directory containing all the files that need to go on your web server.

Note that

yarn dist

yarn build

webapp

webapp

Running as a Desktop app

Element can also be run as a desktop app, wrapped in Electron. You can download a pre-built version from https://element.io/get-started or, if you prefer, build it yourself.

To build it yourself, follow the instructions at https://github.com/vector-im/element-desktop.

Many thanks to @aviraldg for the initial work on the Electron integration.

Other options for running as a desktop app: * @asdf:matrix.org points out that you can use nativefier and it just works(tm)

yarn global add nativefier
nativefier https://app.element.io/

The configuration docs show how to override the desktop app's default settings if desired.

Running from Docker

The Docker image can be used to serve element-web as a web server. The easiest way to use it is to use the prebuilt image:

bash
docker run -p 80:80 vectorim/riot-web

To supply your own custom

config.json

/app/config.json

/etc/element-web/config.json

bash
docker run -p 80:80 -v /etc/element-web/config.json:/app/config.json vectorim/riot-web

To build the image yourself:

bash
git clone https://github.com/vector-im/element-web.git element-web
cd element-web
git checkout master
docker build .

If you're building a custom branch, or want to use the develop branch, check out the appropriate element-web branch and then run:

bash
docker build -t \
    --build-arg USE_CUSTOM_SDKS=true \
    --build-arg REACT_SDK_REPO="https://github.com/matrix-org/matrix-react-sdk.git" \
    --build-arg REACT_SDK_BRANCH="develop" \
    --build-arg JS_SDK_REPO="https://github.com/matrix-org/matrix-js-sdk.git" \
    --build-arg JS_SDK_BRANCH="develop" \
    .

config.json

Element supports a variety of settings to configure default servers, behaviour, themes, etc. See the configuration docs for more details.

Labs Features

Some features of Element may be enabled by flags in the

Labs

Caching requirements

Element requires the following URLs not to be cached, when/if you are serving Element from your own webserver:

/config.*.json
/i18n
/home
/sites
/index.html

Development

Before attempting to develop on Element you must read the developer guide for

matrix-react-sdk

Before starting work on a feature, it's best to ensure your plan aligns well with our vision for Element. Please chat with the team in #element-dev:matrix.org before you start so we can ensure it's something we'd be willing to merge.

You should also familiarise yourself with the "Here be Dragons" guide to the tame & not-so-tame dragons (gotchas) which exist in the codebase.

The idea of Element is to be a relatively lightweight "skin" of customisations on top of the underlying

matrix-react-sdk

matrix-react-sdk

After creating a new component you must run

yarn reskindex

component-index.js

Please note that Element is intended to run correctly without access to the public internet. So please don't depend on resources (JS libs, CSS, images, fonts) hosted by external CDNs or servers but instead please package all dependencies into Element itself.

Setting up a dev environment

Much of the functionality in Element is actually in the

matrix-react-sdk

matrix-js-sdk

develop

First clone and build

matrix-js-sdk

git clone https://github.com/matrix-org/matrix-js-sdk.git
pushd matrix-js-sdk
yarn link
yarn install
popd

Then similarly with

matrix-react-sdk

git clone https://github.com/matrix-org/matrix-react-sdk.git
pushd matrix-react-sdk
yarn link
yarn link matrix-js-sdk
yarn install
popd

Finally, build and start Element itself:

git clone https://github.com/vector-im/element-web.git
cd element-web
yarn link matrix-js-sdk
yarn link matrix-react-sdk
yarn install
yarn start

Wait a few seconds for the initial build to finish; you should see something like:

Hash: b0af76309dd56d7275c8
Version: webpack 1.12.14
Time: 14533ms
         Asset     Size  Chunks             Chunk Names
     bundle.js   4.2 MB       0  [emitted]  main
    bundle.css  91.5 kB       0  [emitted]  main
 bundle.js.map  5.29 MB       0  [emitted]  main
bundle.css.map   116 kB       0  [emitted]  main
    + 1013 hidden modules

Configure the app by copying

config.sample.json

config.json

Open http://127.0.0.1:8080/ in your browser to see your newly built Element.

Note: The build script uses inotify by default on Linux to monitor directories for changes. If the inotify watch limit is too low your build will silently fail. To avoid this issue, we recommend a limit of at least 128M.

To set a new inotify watch limit, execute:

$ sudo sysctl fs.inotify.max_user_watches=131072
$ sudo sysctl -p

If you wish, you can make this new limit permanent, by executing:

$ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
$ sudo sysctl -p

When you make changes to

matrix-react-sdk

matrix-js-sdk

If you add or remove any components from the Element skin, you will need to rebuild the skin's index by running,

yarn reskindex

If any of these steps error with,

file table overflow

ulimit -Sn 1024

Running the tests

There are a number of application-level tests in the

tests

• Make sure you have Chrome installed (a recent version, like 59)
• Make sure you have

  matrix-js-sdk

  and

  matrix-react-sdk

  installed and built, as above

• yarn test

The above will run the tests under Chrome in a

headless

You can also tell karma to run the tests in a loop (every time the source changes), in an instance of Chrome on your desktop, with

yarn
test-multi

End-to-End tests

See matrix-react-sdk how to run the end-to-end tests.

Translations

To add a new translation, head to the translating doc.

For a developer guide, see the translating dev doc.

Triaging issues

Issues will be triaged by the core team using the below set of tags.

Tags are meant to be used in combination - e.g.: * P1 critical bug == really urgent stuff that should be next in the bugfixing todo list * "release blocker" == stuff which is blocking us from cutting the next release. * P1 feature type:voip == what VoIP features should we be working on next?

priority: compulsory

• P1: top priority - i.e. pool of stuff which we should be working on next
• P2: still need to fix, but lower than P1
• P3: non-urgent
• P4: interesting idea - bluesky some day
• P5: recorded for posterity/to avoid duplicates. No intention to resolves right now.

bug or feature: compulsory

• bug
• feature

bug severity: compulsory, if bug

• critical - whole app doesn't work
• major - entire feature doesn't work
• minor - partially broken feature (but still usable)
• cosmetic - feature works functionally but UI/UX is broken

types * type:* - refers to a particular part of the app; used to filter bugs on a given topic - e.g. VOIP, signup, timeline, etc.

additional categories (self-explanatory):

• release blocker
• ui/ux (think of this as cosmetic)
• network (specific to network conditions)
• platform specific
• accessibility
• maintenance
• performance
• i18n
• blocked - whether this issue currently can't be progressed due to outside factors

community engagement * easy * hacktoberfest * bounty? - proposal to be included in a bounty programme * bounty - included in Status Open Bounty