Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Absence of EnvironmentOptions properties and Create event never fired

Open
#3 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
desktop

Research direction

Start by inspecting the ucWebView2 and WebView21 initialization paths, especially EnvironmentOptions handling and when the Create event is raised. No files or tests are named; done means exposing the requested EnvironmentOptions properties, reliably firing Create after initialization, and providing a way to avoid or reinitialize the default page setup.

Written by the indexing model from the issue text.

Description

Hi Jon,

I tested your ucWebView2 component, and it works reasonably well.

I encountered a significant problem: the absence of the EnvironmentOptions property with its sub-properties, such as UserDataFolder for example, but especially the fact that the Create event is never fired.
It is therefore impossible, for example, to define a user data folder different from the default one.

Regarding EnvironmentOptions, I recreated the sub-properties, but for the Create event, I haven't found a solution.
I've been tracking things down! It seems that the WebView21 component fires its Create event before the complete initialization of the control (perhaps during the default loading of the twinbasic.com page!!!). I haven't found a way to delay this initialization.

I find it a shame that in the Webview2 component of TwinBasic, the display of twinbasic.com is permanent (I know it, I bought it!! ;-)) and that there isn't a Reset or ReInit function that initializes the control.

Do you have a solution?
Best regards
François

Dominant language
No language data
Stars
21
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fafalone/ucWebView2

All issues in fafalone/ucWebView2

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.