ForNeVeR / ForNeVeR/omea

Migrate to alternative web view control

Open
#18 0 comments 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
C#
Stars
19
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently, Omea relies on the Internet Explorer engine (e.g. to show the blog posts and whatnot): the only possible solution in the days it was developed, but no longer an acceptable one.

We should migrate to some embeddable Chromium variant instead — and make sure it's properly sandboxed.

Contributor guide

Open the contributing guide

Research direction

Start by locating where Omea currently uses the Internet Explorer engine to display blog posts and other content. Evaluate an embeddable Chromium alternative and its sandboxing requirements; done means the existing web views use the new control and are properly sandboxed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, security
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.