|
| 1 | +// Copyright © 2022 The CefSharp Authors. All rights reserved. |
| 2 | +// |
| 3 | +// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file. |
| 4 | + |
| 5 | +using CefSharp.WinForms.Host; |
| 6 | +using System; |
| 7 | +using System.ComponentModel; |
| 8 | +using System.Windows.Forms; |
| 9 | + |
| 10 | +namespace CefSharp.WinForms |
| 11 | +{ |
| 12 | + /// <summary> |
| 13 | + /// Winforms Specific Chromium browser implementation, differs from <see cref="IWinFormsWebBrowser"/> in that |
| 14 | + /// this interface is implemented by both <see cref="ChromiumWebBrowser"/> and <see cref="ChromiumHostControl"/> |
| 15 | + /// where <see cref="IWinFormsWebBrowser"/> is only implemented by <see cref="ChromiumWebBrowser"/> |
| 16 | + /// </summary> |
| 17 | + public interface IWinFormsChromiumWebBrowser : IChromiumWebBrowserBase, IWin32Window, IComponent, ISynchronizeInvoke |
| 18 | + { |
| 19 | + /// <summary> |
| 20 | + /// Occurs when the browser title changed. |
| 21 | + /// It's important to note this event is fired on a CEF UI thread, which by default is not the same as your application UI |
| 22 | + /// thread. It is unwise to block on this thread for any length of time as your browser will become unresponsive and/or hang.. |
| 23 | + /// To access UI elements you'll need to Invoke/Dispatch onto the UI Thread. |
| 24 | + /// </summary> |
| 25 | + event EventHandler<TitleChangedEventArgs> TitleChanged; |
| 26 | + /// <summary> |
| 27 | + /// Occurs when the browser address changed. |
| 28 | + /// It's important to note this event is fired on a CEF UI thread, which by default is not the same as your application UI |
| 29 | + /// thread. It is unwise to block on this thread for any length of time as your browser will become unresponsive and/or hang.. |
| 30 | + /// To access UI elements you'll need to Invoke/Dispatch onto the UI Thread. |
| 31 | + /// </summary> |
| 32 | + event EventHandler<AddressChangedEventArgs> AddressChanged; |
| 33 | + |
| 34 | + /// <summary> |
| 35 | + /// Event called after the underlying CEF browser instance has been created. |
| 36 | + /// It's important to note this event is fired on a CEF UI thread, which by default is not the same as your application UI |
| 37 | + /// thread. It is unwise to block on this thread for any length of time as your browser will become unresponsive and/or hang.. |
| 38 | + /// To access UI elements you'll need to Invoke/Dispatch onto the UI Thread. |
| 39 | + /// </summary> |
| 40 | + event EventHandler IsBrowserInitializedChanged; |
| 41 | + } |
| 42 | +} |
0 commit comments