[pull] master from cefsharp:master

.editorconfig

@@ -156,3 +156,5 @@ csharp_space_between_square_brackets                                           =
 # Modifier order
 csharp_preferred_modifier_order                                                = public,private,protected,internal,static,extern,new,virtual,abstract,sealed,override,readonly,unsafe,volatile,async : error
 
+# CA2247: Argument passed to TaskCompletionSource constructor should be TaskCreationOptions enum instead of TaskContinuationOptions enum
+dotnet_diagnostic.CA2247.severity = error

.github/FUNDING.yml

@@ -8,6 +8,6 @@
 #community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
 #custom: # Replace with a single custom sponsorship URL
 
-#github: amaitland
-patreon: alexmaitland
+github: amaitland
+#patreon: alexmaitland
 custom: https://paypal.me/AlexMaitland

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,155 @@
+name: Bug Report
+description: Create a report for a reproducible bug
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please only open an issue if you have a **BUG** to report. for questions/assistance use [Discussions](https://github.com/cefsharp/CefSharp/discussions). If you are new to the project then please review the following:
+        1. [General Usage guide](https://github.com/cefsharp/CefSharp/wiki/General-Usage) includes examples and details of many common questions.
+        2. [Frequently Asked Questions](https://github.com/cefsharp/CefSharp/wiki/Frequently-asked-questions), lots of useful information there, specially if your having trouble deploying to a different machine.
+        3. GitHub has a fantastic search feature, it'll search through past issues/code. Use the Search box at the top of this page).
+        4. You can see all the `CefSharp` tagged issues on [Stackoverflow](http://stackoverflow.com/questions/tagged/cefsharp), lots of questions/answers.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+      - label: I have searched both open/closed issues, no issue already exists.
+        required: true
+  - type: input
+    id: cefsharp-version
+    attributes:
+      label: CefSharp Version
+      description: What version are you using? Please only open an issue if you can reproduce the problem with version 145.0.260 or later.
+      placeholder: 145.0.260
+    validations:
+      required: true
+  - type: dropdown
+    id: operating-system
+    attributes:
+      label: Operating System
+      multiple: false
+      options:
+        - Windows 10
+        - Windows 11
+        - Windows Server 2016
+        - Windows Server 2019
+        - Windows Server 2022
+        - Windows Server 2025
+    validations:
+      required: true
+  - type: dropdown
+    id: architecture
+    attributes:
+      label: Architecture
+      multiple: false
+      options:
+        - x64
+        - x86
+        - arm64
+        - AnyCPU
+    validations:
+      required: true
+  - type: input
+    id: dotnet-version
+    attributes:
+      label: .Net Version
+      description: |
+        What .Net version are you using?
+      placeholder: e.g. .Net 4.8 or .Net 6.0
+    validations:
+      required: true
+  - type: dropdown
+    id: cefsharp-implementation
+    attributes:
+      label: Implementation
+      multiple: false
+      options:
+        - WinForms
+        - WPF
+        - WPF HwndHost
+        - OffScreen
+    validations:
+      required: true
+  - type: textarea
+    id: repro-steps
+    attributes:
+      label: Reproduction Steps
+      description: |
+        Please include minimal steps to reproduce the problem. E.g.: the smallest possible code snippet; or a small example project here on GitHub, with steps to run it. Include text/code as text rather than screenshots (so it shows up in searches and can copy/paste).
+        Does the problem reproduce using the [MinimalExample](https://github.com/cefsharp/CefSharp.MinimalExample)? You can fork the MinimalExample and use this as a base for your example.
+      placeholder: Minimal Reproduction
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: |
+        Provide a description of the expected behavior.
+      placeholder: Expected behavior
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual behavior
+      description: |
+        Provide a description of the actual behavior observed. If applicable please include any error messages, exception or stacktraces.
+      placeholder: Actual behavior
+    validations:
+      required: true
+  - type: textarea
+    id: regression
+    attributes:
+      label: Regression?
+      description: |
+        Did this work in a previous build or release of CefSharp? If you can try a previous release or build to find out, that can help us narrow down the problem. If you don't know, that's OK.
+      placeholder: Regression?
+    validations:
+      required: false
+  - type: textarea
+    id: known-workarounds
+    attributes:
+      label: Known Workarounds
+      description: |
+        Please provide a description of any known workarounds.
+      placeholder: Known Workarounds
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        To help determine where the problem needs to be fixed please download and test using the `CEF Sample Application(cefclient)`.
+          1. Download for [x86](https://cef-builds.spotifycdn.com/cef_binary_146.0.7%2Bga6b143f%2Bchromium-146.0.7680.165_windows32_client.tar.bz2) or [x64](https://cef-builds.spotifycdn.com/cef_binary_146.0.7%2Bga6b143f%2Bchromium-146.0.7680.165_windows64_client.tar.bz2) or [arm64](https://cef-builds.spotifycdn.com/cef_binary_146.0.7%2Bga6b143f%2Bchromium-146.0.7680.165_windowsarm64_client.tar.bz2).
+          2. Extract tar.bz2 file
+          3. Execute cefclient.exe using the **command line args below**:
+
+          For WPF/OffScreen `cefclient.exe --multi-threaded-message-loop --no-sandbox --off-screen-rendering-enabled --enable-gpu`
+          For WinForms `cefclient.exe --multi-threaded-message-loop --no-sandbox --use-alloy-style`
+  - type: dropdown
+    id: cefclient-testing
+    attributes:
+      label: Does this problem also occur in the CEF Sample Application
+      multiple: false
+      options:
+        - 'Yes using WPF/OffScreen command line args'
+        - 'Yes using WinForms command line args'
+        - 'No'
+        - Not Tested
+      description: |
+        If you can reproduce the problem with `cefclient` then please report the issue on [CEF Issue Tracker](https://github.com/chromiumembedded/cef/issues) (Make sure you search before opening an issue). If you open an issue here it will most likely be closed as `upstream` as the bug needs to be fixed in `CEF`.
+    validations:
+      required: true
+  - type: textarea
+    id: other-info
+    attributes:
+      label: Other information
+      description: |
+        If you are seeing a crash in `libcef.dll` then please download `libcef.dll.pdb` and place it next to `libcef.dll` to obtain a detailed stack trace, see [FAQ](https://github.com/cefsharp/CefSharp/wiki/Trouble-Shooting#loading-native-symbols-for-easier-diagnosis) for details.
+        Does the cef log provide any relevant information? (By default there should be a debug.log file in your bin directory)
+        Any other background information that's relevant? Are you doing something out of the ordinary? 3rd party controls?
+      placeholder: Other information
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,9 @@
+# https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
+blank_issues_enabled: false
+contact_links:
+  - name: stackoverflow
+    url: http://stackoverflow.com/questions/tagged/cefsharp
+    about: Please ask and answer questions here.
+  - name: Chromium Embedded Framework(CEF) Forum
+    url: https://magpcss.org/ceforum/index.php
+    about: Please ask your non CefSharp specific CEF questions here

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,13 +1,18 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
+about: Suggest an idea for this project, please don't use this template to ask questions, thank you.
 title: Feature Request - My Feature
 labels: feature-request
 assignees: ''
 
 ---
 
-`CefSharp` is a wrapper around the [Chromium Embedded Framework](https://bitbucket.org/chromiumembedded/cef/overview) in a lot of cases a feature must be added to `CEF` first before it can be used in `CefSharp`. `CEF` has it's own `Feature Request Forum` at https://magpcss.org/ceforum/viewforum.php?f=7
+Please ask your questions under the Discussions section here on GitHub 
+- https://github.com/cefsharp/CefSharp/discussions
+
+---
+
+`CefSharp` is a wrapper around the [Chromium Embedded Framework](https://github.com/chromiumembedded/cef) in a lot of cases a feature must be added to `CEF` first before it can be used in `CefSharp`. `CEF` has its own `Feature Request Forum` at https://magpcss.org/ceforum/viewforum.php?f=7
 
 --- 
 
@@ -23,4 +28,4 @@ Add any other context or screenshots about the feature request here.
 **Checklist:**
 - [ ] I have reviewed the [CEF API](https://magpcss.org/ceforum/apidocs3/index-all.html) and have confirmed the feature I'm requesting is possible.
 - [ ] The Feature I'm requesting is an improvement to Async Javascript Binding (No new feature are being added to the Sync Javascript binding)
-- [ ] An open `PR` exists on the [CEF Pull Requests](https://bitbucket.org/chromiumembedded/cef/pull-requests/) and I'd like to propose this feature is added to `CefSharp` when/if it's merged.
+- [ ] An open `PR` exists on the [CEF Pull Requests](https://github.com/chromiumembedded/cef/pulls) and I'd like to propose this feature is added to `CefSharp` when/if it's merged.

.github/config.yml

@@ -9,7 +9,7 @@ newIssueWelcomeComment: >
   <br/>
   <br/>
   It's also important to remember that `CefSharp` is just a wrapper around the `Chromium Embedded Framework(CEF)`, a lot of questions people
-  have aren't actually `CefSharp` specific, they're generic to `CEF` and for those `CEF` has it's own support forum at http://magpcss.org/ceforum/index.php and issue tracker at https://bitbucket.org/chromiumembedded/cef
+  have aren't actually `CefSharp` specific, they're generic to `CEF` and for those `CEF` has it's own support forum at http://magpcss.org/ceforum/index.php and issue tracker at https://github.com/chromiumembedded/cef/issues
   <br/>
   <br/>
 

.github/pull_request_template.md

@@ -1,29 +1,30 @@
-Fixes [issue-number] 
-   - e.g Fixes #2345
+**Fixes:** [issue-number] 
+<!-- e.g Fixes: #2345 -->
 
 **Summary:** [summary of the change and which issue is fixed here]
    - e.g. I have added a new feature to the Javascript Binding implementation
 
 **Changes:** [specify the structures changed] 
-   - e.g. I have modified the Javascript Bindign Implementation
+   - e.g. I have modified the Javascript Binding Implementation
       - Added support for Async binding to return Task<T>
       - Added new QUnit Test cases
 
-## How Has This Been Tested?
-<!--- Please describe in detail how you tested your changes. -->
-<!--- Include details of your testing environment, operating system, and the tests you ran to -->
-<!--- see how your change affects other areas of the code, etc. -->
+**How Has This Been Tested?**  
+<!-- Please describe in detail how you tested your changes. -->
+<!-- Include details of your testing environment, operating system, and the tests you ran to -->
+<!-- see how your change affects other areas of the code, etc. -->
 
-## Screenshots (if appropriate):
+**Screenshots (if appropriate):**
 
-## Types of changes
-<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+**Types of changes**
+<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to change)
 - [ ] Updated documentation
 
 **Checklist:**
+<!-- Put an `x` in all the boxes that apply: -->
 - [ ] Tested the code(if applicable)
 - [ ] Commented my code
 - [ ] Changed the documentation(if applicable)

.github/workflows/codeql-analysis.yml.bak

@@ -0,0 +1,62 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+name: "CodeQL"
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [master]
+  schedule:
+    - cron: '0 4 * * 5'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: windows-latest
+
+    strategy:
+      fail-fast: true
+      matrix:
+        # Override automatic language detection by changing the below list
+        # Supported options are ['csharp', 'cpp', 'go', 'java', 'javascript', 'python']
+        language: ['csharp']
+        # Learn more...
+        # https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v1
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+        # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v1
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 https://git.io/JvXDl
+
+    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+    #    and modify them (or add more) to build your code if your project
+    #    uses a compiled language
+
+    #- run: |
+    #   make bootstrap
+    #   make release
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v1

.gitignore

@@ -21,7 +21,9 @@
 _ReSharper*
 
 bin/
+bin.netcore/
 obj/
+obj.netcore/
 packages/
 Debug/
 Release/
@@ -39,3 +41,4 @@ x64/Release
 Win32/Release
 .vs/
 /Help
+/tools